IBM Support

Unexpected DWO373E when stopping a z/OS system using GDPS

Question & Answer


Question

Customer received a flood of DWO373E messages when stopping a z/OS system from GDPS and wanted to know how to eliminate them.

Cause

SA did not support TRAP/WAIT within commands in SYSTEM_SHUTDOWN policy at the time

Answer

A trace of the situation showed that during the GDPS "STOP" action, normal flow was being carried out to this point in time, where GDPS REXX VPCEFLIP invoked SA z/OS REXX INGRTERM:
       
'STOP OF SYSN STARTED'                                  
VPCEFLIP  CHECKING INGRTERM                            
DWO373E ERROR: IMPROPER TRAPPING OF MESSAGES WITHIN A PIPELINE. DELAY FAILED  

More detailed flow showed SA z/OS rexx INGRTERM was invoking another SA z/OS command (ISSUEACT) to look up and execute SA policy defined commands (under policy entry MVSESA SYSTEM_SHUTDOWN):

AOF700I CLIST INGRTERM EXECUTING ON AUTGEO3 WITH PARMS >  STOP,GDPS,,JES2/APL/sysn,sysn AOF700I CLIST AOFRSGCR EXECUTING ON AUTGEO3 WITH PARMS > AUTOTYP=NOCH ENTRY=MVSESA MSGTYPE=SYSTEM_SHUTDOWN SYSTEMMSG=YES EHKVAR=NO SEL=PHASE0                                                                 AOF700I CLIST AOFRSCMD EXECUTING ON AUTGEO3 WITH PARMS > ENTRY=MVSESA,MSGTYP=SYSTEM_SHUTDOWN,SEL=PHASE0  
DWO373E ERROR: IMPROPER TRAPPING OF MESSAGES WITHIN A PIPELINE. DELAY FAILED                
So, at this point SA has attempted to execute the commands defined by the client under the MVS Components SYSTEM_SHUTDOWN item.

Examination of the DWO373E also reveals that the command submitted is a command called "DELAY". This is not a NetView, SAzOS, or GDPS supplied command.

Customer reviewed their SYSTEM_SHUTDOWN policy definitions and found a local rexx invoked under that entry (entry=MVSESA type=SYSTEM_SHUTDOWN pass=PHASE0), and that rexx invoked TRAP/WAIT NetView services, which is not allowed when the command is invoked in a pipe (many SA and GDPS services are invoked using NetView PIPEs). Hence, that is the reason for the DWO373E message.

Once the client removed the offending local rexx or re-wrote it to avoid TRAP/WAIT processing then the DWO373E messages were eliminated.

Note: subsequent to creation of this document, SA has released APAR OA43535 which provides support to allow clients to define any commands in SYSTEM_SHUTDOWN that utilize TRAP/WAIT. GDPS subsequently provided APAR PI06224 to be compatible with this SA APAR.

[{"Product":{"code":"SSWRCJ","label":"IBM Tivoli System Automation for z\/OS"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"--","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Historical Number

49748;999;631

Product Synonym

GDPS SA SAz SAzOS SAfzOS

Document Information

Modified date:
08 August 2018

UID

swg21651773