z/OS - Group home

#002 Change on ROUTE command via MGCRE with CMDFLAG=(NOHCPY)

By Shigeki Kimura posted Sun July 19, 2020 07:35 AM

  
You might observe this intended change on ROUTE command via MGCRE with CMDFLAG=(NOHCPY) when upgrading to z/OS V2R4.

Specifying CMDFLAG=(NOHCPY) parameter on MGCRE macro requests the subject command be suppressed from the hardcopy log (ie. SYSLOG or OPERLOG). However, for a ROUTE command issued via MGCRE with CMDFLAG=(NOHCPY), the ROUTE command itself is suppressed from hardcopy but the command being "routed" will still be in the hardcopy log.

This behavior has been changed in z/OS V2R4 via APAR OA55640 (January 2020).

After the PTF for APAR OA55640 is applied, when ROUTE is issued via MGCRE with CMDFLAG=(NOHCPY) specified, NOHCPY will scope to both the ROUTE command itself and the target command being "routed".
- If you do not specify CMDFLAG=(NOHCPY) parameter, the command is logged in the hardcopy log. For a ROUTE command being issued, the command to be "routed" is also logged.
- If CMDFLAG=(NOHCPY) parameter is specified, the command is not logged in the hardcopy log. For a ROUTE command being issued, the command to be "routed" is also not logged in the hardcopy log.

(Examples)
"D T" command issued via MGCRE
D T
IEE136I LOCAL: TIME=23.47.14 DATE=2020.169 UTC: TIME=14.47.14
DATE=2020.169
"D T" command issued via MGCRE with CMDFLAG=(NOHCPY)
IEE136I LOCAL: TIME=23.47.14 DATE=2020.169 UTC: TIME=14.47.14
DATE=2020.169
"ROUTE xxxx, D T" command issued via MGCRE
RO xxxx,D T
D T
IEE136I LOCAL: TIME=23.47.14 DATE=2020.169 UTC: TIME=14.47.14
DATE=2020.169
(Before APAR OA55640) "ROUTE xxxx, D T" command issued via MGCRE with CMDFLAG=(NOHCPY)
D T
IEE136I LOCAL: TIME=23.47.14 DATE=2020.169 UTC: TIME=14.47.14
DATE=2020.169
(After APAR OA55640) "ROUTE xxxx, D T" command issued via MGCRE with CMDFLAG=(NOHCPY)
IEE136I LOCAL: TIME=10.12.13 DATE=2020.176 UTC: TIME=01.12.13
DATE=2020.176

Hope it helps you.
Thanks!
0 comments
26 views