In any of the various members that HTAC accesses from PARMLIB members (stored in the PDS referenced by the HBPARMS DD statement in the CICS startup deck), there are several common coding conventions.  They are as follows:

  • Specifying an * in column 1 of a record containing a directive or directives indicate that that record is to be treated as a comment and not processed as a directive.
  • Specifying // in columns 1-2 of a record followed by spaces indicates that directive processing should terminate and any records following it should be ignored.
  • Specifying #INCLUDE= in columns 1-9 followed by a character string ended by a semicolon ( ; ) indicates that a member with the name equaling the character string exists in the PARMLIB PDS and should be immediately processed for directives.

    An example of a #INCLUDE command would be #INCLUDE=EXTRADIR;, where EXTRADIR would be a member within the HBPARMS PDS.

    You can generalize the INCLUDE by specifying symbolic names within the character string.  Valid symbolic names are &APPLID (the CICS applid), &SYSID (the CICS sysid), &TRANID (name of the CICS transaction currently being executed), and &PROGRAM (name of the CICS program currently being executed).   Therefore, a character string of HBXX&SYSID would generalize to HBXXCICE if CICE was the SYSID of the region where the directives were being processed, and the member HBXXCICE would need to exist in the HBPARMS PDS.  Be sure to code a semicolon at the end of the statement (#INCLUDE=HBXX&SYSID:)


© 2022 HostBridge Technology, LLC
Unless otherwise noted, all rights reserved.