In this instance the IDCAMS command represents a NETVIEW command:
CMDDEF.IDCAMS.MOD=DSIDCAMS
CMDDEF.IDCAMS.FOLDUP=Y
DISPMOD DSIDCAMS
CNM263I MODULE LENGTH CSECT DATE PTF EPA AM ATTR
CNM263I DSIDCAMS 000570 DSIDCAMS 05/30/14 ------- 000291B0 24 RN RU
CNM265I END OF DISPLAY
In my example, I am running Netview V6.2.1. I believe that the intent
here was to provide a method for Netview to runs IDCAMS "maintenance" functions
on the various Netview Databases; NLDM, NPDA, TARA etc, without the need to
recycle the Netview tasks. I do use them for such maintenance, but they run
infrequently.
I don't claim to understand the relationship/difference between using
the Netview IDCAMS command and the TSO or batch flavor, but it likely that the
storage issue is related to how Netview invokes IDCAMS.
It might be help to route this question/issue to the Netview users
group. I believe that they are at Groups.io.
Hth
Tony
-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of
Paul Gilmartin
Sent: Wednesday, May 20, 2020 12:26 PM
To: [email protected]
Subject: Re: REXX assistance
[[ SEI WARNING *** This email was sent from an external source. Do not open
attachments or click on links from unknown or suspicious senders. *** ]]
On Wed, 20 May 2020 06:45:57 -0500, Dave Jousma wrote:
>All,
> ...
In a JCL example in
https://www.ibm.com/support/knowledgecenter/zosbasics/com.ibm.zos.zdatamgmt/zsysprogc_utilities_IDCAMS.htm
I see:
//SYSPRINT DD *
Is that probably what the writer intended? Is it even legal?
Writers should hand their examples back to coders for review and testing.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
[email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
