The following issues are addressed in JAMS for OpenVMS Version 4.2M
- Specifying an empty string ("") as the parameter for the JAMS SET ENTRY command was being interpreted as an * wildcard.
- JAMS command lines can now be up to 8192 bytes long.
- If you have a job or setup name with the maximum length of a name (39 characters), history searches might never complete.
- In rare instances, using the JAMS SYNCHRONIZE command could cause the JAMS_SCHEDULE process to hang waiting for a lock to be granted.
Comments