JAMS for OpenVMS V4.2M


The following issues are addressed in JAMS for OpenVMS Version 4.2M

  1. Specifying an empty string ("") as the parameter for the JAMS SET ENTRY command was being interpreted as an * wildcard.
  2. JAMS command lines can now be up to 8192 bytes long.
  3. If you have a job or setup name with the maximum length of a name (39 characters), history searches might never complete.
  4. In rare instances, using the JAMS SYNCHRONIZE command could cause the JAMS_SCHEDULE process to hang waiting for a lock to be granted. 
Have more questions? Submit a request