It looks like the Netview IDCAMS command accepts at most two parameters
that must be DDNAMEs. The second DDNAME will default to SYSPRINT if not
specified. The DDNAMEs are basically INPUT and OUTPUT files. So the INPUT file
must be built prior to invoking the Netview IDCAMS command.
The DSIVSMX IDCAMS command also calls the IDCAMS utility, but the
IDCAMS control statements are read from the message that started the DSIVSMX
command. This is more conducive to being used within a PIPE with a STEM
variable as the input stream.
The Netview help for DSIVSMX IDCAMS (Option F) references those same
Netview samples; CNMS8013, CNMS8014, CNMS8015 and CNMS8020.
Also, the groups.io group or Netview can be found here:
https://groups.io/g/NetView
Hth
Tony
-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of
Jousma, David
Sent: Wednesday, May 20, 2020 1:19 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. *** ]]
Thanks Tony. I see that IDCAMS used within netview is a valid netview command.
But then I see this in the netview samplib
Define_Base_Cluster_VSAM_File:
/* Called by Define_and_Load_Base_Cluster*/
SAY 'Attempting to define the VSAM file....'basename
k.0 = 14
k.1 = ' DEFINE CLUSTER -'
k.2 = ' (NAME ('basename') -'
k.3 = ' INDEXED -'
k.4 = ' KEYS('key_size RKP') -'
k.5 = ' SHAREOPTIONS('shr1 shr2') -'
k.6 = ' RECORDSIZE('avg_recsize max_recsize') -'
k.7 = ' VOLUMES(CPDLB2) -'
k.8 = ' NOREUSE ) -'
k.9 = ' DATA -'
k.10 = ' (NAME ('basename'.DATA) -'
k.11 = ' CYLINDERS('data_size') ) -'
k.12 = ' INDEX -'
k.13 = ' (NAME ('basename'.INDEX) -'
k.14 = ' CYLINDERS('index_size') )'
'PIPE STEM k.|COLLECT|NETV MOE DSIVSMX IDCAMS|STEM R1.'
What purpose is the last line, specifically the NETV MOE DSIVSMX IDCAMS
portion? Why not just NETV MOE IDCAMS? According to the fine manual
DSIVSMX is labelled as a "command processor". Does that imply setting up an
environment? I've asked IBM these questions too.
IBM Tivoli NetView for z/OS, Version 6.2 The DSIVSMX command processor can
define, read, and write VSAM keyed files directly from REXX without using data
services tasks. This enables the implementation of VSAM applications, including
end-use application development in REXX (in conjunction with the pipeline
facility), and intensive VSAM diagnostics.
The DSIVSMX command provides REXX access to keyed VSAM files and to IDCAMS, the
VSAM Access Method Services utility.
_____________________________________________________________________________________________________
Dave Jousma
AVP | Manager, Systems Engineering
Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI
49546
616.653.8429 | fax: 616.653.2717
-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of
Cieri, Anthony
Sent: Wednesday, May 20, 2020 1:02 PM
To: [email protected]
Subject: Re: REXX assistance
**CAUTION EXTERNAL EMAIL**
**DO NOT open attachments or click on links from unknown senders or unexpected
emails**
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 **CAUTION EXTERNAL
EMAIL**
**DO NOT open attachments or click on links from unknown senders or unexpected
emails**
This e-mail transmission contains information that is confidential and may be
privileged. It is intended only for the addressee(s) named above. If you
receive this e-mail in error, please do not read, copy or disseminate it in any
manner. If you are not the intended recipient, any disclosure, copying,
distribution or use of the contents of this information is prohibited. Please
reply to the message immediately by informing the sender that the message was
misdirected. After replying, please erase it from your computer system. Your
assistance in correcting this error is appreciated.
----------------------------------------------------------------------
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
