A 2 quick question.
Did you look up the syntax in the manual?
Or do an internet search using: ibm commndxx syntax
The following rules apply to the creation of COMMNDxx:
Enter only one command per line. To do so, specify the COM=keyword,
followed by the command enclosed in single quotation marks. For example, to
start TCAM through use of the IBM-supplied PROC, enter COM='S TCAM'.
Do not specify continuation on any line.
Do not specify comments.
Do not use COMMNDxx to enter MONITOR commands. Instead, use the SETCON
MONITOR command to enable or disable Monitor messages.
A command placed in COMMNDxx must look exactly as it does if entered from the
console. For example, to place the command SE 'TSO IS UP', CN=CONS1 in
COMMNDxx, specify the following:
COM='SE 'TSO IS UP',CN=CONS1'
System commands in COMMNDxx can specify system symbols. System symbols can
represent any type of variable text in system commands, with the exception of
command prefixes and names.
The following is an example of a COMMNDxx member that includes system symbols.
a sample IEASYMxx member that defines the system symbols in this COMMNDxx
member.
. Example COMMNDxx Parmlib Member
COM='S VTAM,,,(LIST=&NODE;)'
COM='S NETVIEW,SUB=MSTR,CAT=&CATALOG;,SYS=&SYSNAME;'
COM='S APPC,SUB=MSTR,APPC=02'
COM='S ICR&SYSNAME;.SYSLOG'
COM='SET DAE=01'
COM='SET DAE=&DAE;'
COM='SETXCF START,POLICY,TYPE=CFRM,POLNAME=&POLNAME;'
Be aware that the system does not process system symbols in COMMNDxx during
parmlib processing. Instead, the system processes the system symbols in the
same way that it processes system symbols in commands that are entered on a
console. When a command flows through two or more systems in a sysplex, the
target system processes the system symbols in the command text, with a few
exceptions. See the topic on sharing system commands in z/OS MVS Planning:
Operations for details about how the system processes system symbols in
commands that flow through two or more systems.
As others have pointed out - what you enter on the console is what you would
place between the quotes on the COM= line.
Lizette
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On
> Behalf Of suresh chacko
> Sent: Monday, June 23, 2014 4:41 AM
> To: [email protected]
> Subject: COMMANDxx member
>
> Hi
>
> I need a help in coding syntax of z/OS COMMANDxx of PARMLIB. Please note
> that our installation is not sysplex and 4 LPARS connected with GRS in CEC's,
> one
> at Primary site and the other at secondary site. We are on z/OS 1.12. The
> below are
> for the automatic dump data sets allocation coded in the COMMANDxx.
>
> I have three questions here:-
>
> 1. Can I use multiple volumes in this scenario. If so how I can code? ( I
> understood i
> can't use shared volumes as our is not a sysplex).
> 2. COM='DUMPDS ADD,VOL=(VOLUM1,VOLUM2)' - is this coding valid in our
> case?
> 3. Which coding is correct from the below? I believe CHG DUMP VIRTUAL STOR
> TO 2G which is starting after 2048M is a comment..Am I right?
> ------------------------------
> a. COM='CD SET,SDUMP,MAXSPACE=2048M CHG DUMP VIRTUAL STOR
> TO 2G'
>
> b. COM='CD SET,SDUMP,MAXSPACE=2048M CHG DUMP VIRTUAL STOR
> TO 2G'
>
> I noticed in all other statements in COMMANDxx, comments (I assume) are
> starting
> after the commands with a gap of minimum 2 empty spaces like the second one.
> If
> I am wrong please correct me
>
> Please advise.
>
> Thanks,
> Suresh N
>
> ----------------------------------------------------------------------
> 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
