August 2017
Version: 1.11
-
A problem causing an internal locking mechanism to fail to perform an unlock, resulting in the failure of a monitored command, has been resolved. (The associated job where the command was being executed from displayed a consistent status of SEMW.)
April 2017
Version: 1.10
- A loophole where the internal semaphore unlock failed to occur has been closed.
- The initial sentence of the help text for the PCSJRNRPT command, which incorrectly referenced a Command Security setting, has been corrected.
- F5 (Refresh) for PCS2880 no longer causes an error when the list it displays contains no entries.
- PCS2880 no longer displays the incorrect text when the list is empty. (Previously the copyright message would appear in this case. Now the correct message, that no data exists, is displayed.)
July 2016
Version: 1.09
- Command Security is now delivered with new deployment functionality, including the ability to stage the product installation.
- Failure to prompt and subsequently execute a monitored command due to a duplicate command name in different library has been resolved.
- Panel PCS3231’s screen legend for “Ignore text case” has been changed to more accurately reflect the nature of the parameter.
- A new utility program, PCS9990, has been added to the product. This program can be used if one of the system semaphores used by Command Security becomes “stuck” and is adversely affecting product functionality.
December 2015
Version 1.08
- The handling of proxy commands has been modified in order to work with new IBM PTFs.
- The F9=Retrieve function now works for monitored commands.
- The Remove Keyword function (*RMVKWD) no longer overwrites the previous keyword in some cases.
- Licensing updates.
July 2014
Version: 1.07
- The installation procedure has been modified to retain existing special authorities for PTADMIN.
- The validation on keyword type NAME has been changed to allow special values (values that start with *).
April 2014
Version 1.06
- Network Security displays the appropriate descriptions when creating a condition with Data Source *JOBTYPE.
- Command Security now finds any program in your call stack when a condition has been created to check for one.
- Rules employing the MSG Action no longer send incorrect messages when conditions are met.
- Object validation now allows 10-character library names.
August 2013
Version: 1.04
- Added system information to report headings
Version: 1.05
- Fix update lock when product fails with “Objects are locked in PTCSLIB”.
- Correct problem when Journal Report fails with “Message ID not found”
- New Data Sources for Condition checking (*ACGCDE, *JOBUSER, *LMTCPB, *SPCAUT, *USRCLS, *USRPGM)
- New Action (*QUEUEMSG) which sends a message to a message queue
May 2013
Version: 1.03
- Correctly handle MEMBEROF condition when multiple values are entered.