Migration considerations for network security credential propagation enhancement
There are several migration considerations related to the network security credential propagation enhancement.
-
If the security-data section of the OTMA message prefix contains network security credentials, the size of the OTMA message can increase by up to 504 bytes. Therefore, consider increasing the size of the SHMSG and LGMSG message queue data sets and the size of the message queue pool.
-
If both of the following situations occur, you might need to modify code that includes the HWSOMPFX macro:
- The Network Session ID (NETSID) section or the Network User ID (NETUID) section, or both, is included in the security section of the OTMA message header.
- Either the DSECT=ALL or the DSECT=NO option is specified with the HWSOMPFX macro.
For the fields of the OTMA message header that are below the security section to be accessed, you need to map the HWSOMUSR, HWSOMAPP, or HWSOMAPX DSECTS of the HWSOMPFX macro to the changed locations of the fields.
For more information about the fields of the OTMA message header, see OTMA header fields used by IMS Connect.
- In IMS 15, processing by the HWSJAVA0 user
message exit routine of the user data section that is in the OTMA message header is updated. If the
OTMA message header contains network security information and the HWSOMPFX macro is used, the
HWSJAVA0 exit routine specifies both the DSECT= and the
NETSEC_OPT=YES options for the HWSOMPFX macro. The
DSECT= and the NETSEC_OPT=YES options
cause the following behaviors:
- An individual DSECT is generated for each section of the OTMA message header.
- The HWSECDNDS DSECT, or the HWSECARDS DSECT, or both, is generated to map network security information.
- The HWSOMPFX DSECT is not generated.