CICS

• An EXEC CICS DELAY statement may sometimes produce a difference of one second.
• EXEC CICS VERIFY PASSWORD has a failure scenario that doesn't exist on the mainframe. It is currently not possible to distinguish this failure from an incorrect password on the command itself via the returned EIBRESP and EIBRESP2.

  Under Enterprise Server, the following options mean that an admin LIST request to ESF is necessary to acquire the appropriate information:

  • CHANGETIME
  • DAYSLEFT
  • EXPIRYTIME
  • INVALIDCOUNT
  • LASTUSETIME

  If no users are signed on to CICS, then this admin request will be made as the default CICSUSER which will be rejected.

  The VERIFY PASSWORD command will return NOTAUTH 2, "The supplied password is wrong".

  This is misleading because it implies that the value for PASSWORD on the command itself is incorrect. Note that in that case, CICS returns NOTAUTH 2 as per the mainframe.

  The aggregated return code from ESF to CICS for the admin request is identical in both cases and so CICS has no way of distinguishing between these two failure scenarios. We therefore cannot return a new EIBRESP or EIBRESP2 for this particular case.

  To allow CICSUSER to make admin LIST requests, the anonymous list option needs to be enable in the region's security manager configuration (not the Security Manager):

  [Admin]
  allow-list=yes

CICS file control has the following limitations:

• Neither CICS- nor user-maintained data tables are supported. From an application programming point of view, this limitation has little or no impact. From a systems programming perspective, you will not have the ability to eliminate disc I/O activity by defining user-maintained tables.