PTF LU06367 - ARM JES2 EXIT6 IS DISABLED IF IT MISMATCHES JES2 LEVEL
Article ID: 249690
Updated On:
Products
Issue/Introduction
I need an explanation about the holddata of PTF LU06367
----------
Verify that the Vantage KNGED009 module has been assembled with the
correct JES2 SHASMAC libraries for the current z/OS version.
If it is not, make sure to reassemble it before this PTF is applied
to prevent ARM JES2 Exit6 processing from being automatically disabled
by Vantage due to the mismatched level.
The level can be checked by looking at the MIT eye catcher in the
KNGED009 load module. It should look like this:
"MIT KNGJES2Xz/OS x.x"
where x.x is the version of z/OS that the module was assembled for.
------------
Resolution
In case a user system is running on a z/OS version older than 2.5, for instance, z/OS 2.4, once PTF LU06367 is applied, it is recommended to reinstall the JES2 exit as the SAMUM04 usermod, which can be done using the KNGED009 member of the CCTUSAMP library.
This job assembles and links a new copy (matching the current z/OS version) of the KNGED009 load module into CCTULOAD.
This is described in more detail in the "SYSPROG - Configure Extended ARM Support for JES2" section of the article:
Configure the Auto Restore Manager (ARM) - Enhance DMSAR
SYSPROG - Configure Extended ARM Support for JES2
More information on the available usermods (including SAMUM04) can be found here:
Additional Information
Additional background/scenarios concerning update of the KNGED009 module:
Scenario #1: Vantage 14.1 without ARM support for Disk Backup and Restore:
If the system is not using Vantage 14.1 with Disk Backup and Restore support with the Auto Restore Manager (ARM) function enabled, then no action is required regardless of the Vantage version, Disk Backup and Restore status, ARM configuration, z/OS version, or maintenance level.
Scenario #2: Vantage is running with ARM support for Disk Backup and Restore:
If ARM support is active, the reassembly of the KNGED009 module is always required, as specified in the Vantage product documentation and HOLDDATA, independent of other product maintenance levels or the z/OS version.
Examples for Scenario #2 include:
Upgrading from Vantage 14.0 to 14.1 on z/OS 2.4 → Reassemble KNGED009
Upgrading z/OS 2.4 to 2.5 with Vantage 14.1 → Reassemble KNGED009
Applying the latest Vantage 14.1 maintenance related to KNGDE009 on z/OS 2.5 → Reassemble KNGED009
Upgrading z/OS 2.5 to 3.1 with the latest Vantage 14.1 maintenance → Reassemble KNGED009
A specific example of a customer scenario:
Module KNGED009 information: “MIT KNGJES2Xz/OS 2.4 .J.&6...HJE77C0 08/05/2102.13 “
This KNGED009 module information indicates that someone correctly reassembled the KNGED009 module in the system, based on the applicable HOLDDATA or documentation for this customer site. (Note: The factory-delivered version of KNGED009 was originally assembled on z/OS 2.2.)
Current customer situation: Vantage PTF LU06367 is not installed yet:
(Note: The Vantage team is aware that the HOLDDATA for this PTF contains incorrect instructions. It incorrectly states that the reassembly of KNGED009 should occur before applying the PTF. The correct sequence is to perform the reassembly AFTER applying PTF LU06367).
Scenarios related to installation of LU06367:
a) If you do not apply Vantage PTF LU06367, and using Vantage on any z/OS version:
No message will appear in the system log indicating any mismatch, regardless of your Disk Backup Restore or z/OS versions, and ARM functionality might be compromised (Note: compromise can actually happen only if you customized the IBM z/OS delivered macros and/or CA Disk Backup Restore factory delivered macros. Uncustomized macros ensures stable and fully functional Vantage+ARM operation without any manual action being required.)
b) If you do apply Vantage PTF LU06367, and you use Vantage, for example on z/OS 3.1 (or 2.4, that is, any z/OS level different from z/OS 2.5):
Once Vantage is started, you will receive a $HASP908 message in the SYSLOG indicating that a mismatch exists between the KNGED009 module and the JES2/z/OS level because the factory-delivered version (via LU06367) was assembled on z/OS 2.5. In this case the ARM stops working. To mitigate this problem you will have to act according to the *corrected* HOLDDATA of LU06367, and reassemble the KNGED009 module prior starting Vantage and Disk.
Feedback
