GP1015 Procedure abend in $IPPT02Z line 3081 when running packet trace.
book
Article ID: 77518
calendar_today
Updated On:
Products
CMDB for z/OSNetSpy Network PerformanceNetMaster Network AutomationSOLVENetMaster Network Management for SNANetMaster Network Management for TCP/IPNetMaster File Transfer Management
Issue/Introduction
Trying to run the Netmaster for TCP/IP 12.1 Smarttrace either with /TRALL or D.TR.L from the main menu results in following error message in log
GP1015 Procedure abend in $IPPT02Z line 3081. NM4014 MDO DATA ASSIGNMENT FAILED, RC= 12 FDBK= 0 GP1016 $IPPT02Z abend details: LINE=3081 COND=VARIABLE_ERROR STMT_NAME== KEYWORD= NAME= SUBNAME=$IPDATA.INSTANCE.{1}.EXPIRYRAW VALUE= VALUEOK=0 VALUE2= VALUE2OK=
Environment
Release: SLOPFC00200-12.1-NetMaster-File Transfer Management Component:
Cause
The cause is PTF related; fixes may be missing, or may be applied without having run the NMVIP jobs contained in the ++HOLD of the PTFs. PTF RO93545 applied. If this job is missing, mapping in the OSCNTL is not in sync with the updates to the related NCL and OML procs and processing fails.
Ensure the following PTFs are applied: RO93545 RO93055 RO92123 (PRE of RO93545)
To verify whether RO93545 (or RO92123) is active in the region, logon to your current region, go to Command Entry (CMD) and issue LIST PROC=$IPPT02Z
You will see the content of the proc returned on the screen. Check the first line. The RMID should contain the PTF number. Z9OMLOBJ0 $IPPT02Z 20161213 162428 070600 004 UTIL 04412 ~RMID(RO93545).
For RO93055: LIST PROC=$IPIS20Z Z9OMLOBJ0 $IPIS20Z 20161109 125639 070600 002 UTIL 00944 ~RMID(RO93055)
If any of the three PTFs is missing, applying them and ensuring they are available in the Netmaster runtime libraries is the first step.
RO92313 and RO93055 both have ++HOLD information in the PTFs instructing that an NMVIP batchjob must be run to copy updated content from the SMP/E VSAM staging files over to the OSCNTL VSAM file.
If this has not been done, the symptoms described in the first section will persist as the content of the OSCNTL will not match the updated procs. The region must be stopped in order to run the update.