Dear Lizette, Thanks a lot. I will try the same too.
Regards, Suresh On Mon, Jun 23, 2014 at 6:23 PM, Lizette Koehler <[email protected]> wrote: > The easiest way to see what works - try the commands. > What does a D D,O command show? > What does a DD T,AUTODSN=ALL > > DD ALLOC={ACTIVE|INACTIVE} > ALLOC=ACTIVE > Dump data sets are automatically allocated when a dump is requested. > Any of the resources that have been defined by the DUMPDS ADD command as > available for automatically allocated dump data sets are used. If no > automatic allocation resources are defined, the system issues message > IEA799I and writes the dump to a pre-allocated dump data set on its list of > SYS1.DUMP data sets. If no pre-allocated dump data sets are on the system's > list of SYS1.DUMP data sets, then message IEA793A is issued requesting > operator intervention. The requested dump is kept in virtual storage until > an automatic allocation resource is defined, a pre-allocated dump data set > is made available either by allocating a new one or clearing an existing > one, or the dump is deleted either by operator request or expiration of the > CHNGDUMP MSGTIME parameter. > > The books show what you can use for symbols in the name. TinyURL: > http://tinyurl.com/lm627uq > > Symbols reserved for system use. When you define additional system > symbols in the IEASYMxx parmlib member (see “Step 5. Create an IEASYMxx > parmlib member” on page 44), ensure that you do not specify the names of > the following system symbols, which are reserved for system use: > &DATE > &DAY > &HHMMSS > &HR > &JDAY > &JOBNAME > &LDATE > &LDAY > &LHHMMSS > &LHR > &LJDAY > &LMIN > &LMON > &LSEC > <IME > &LWDAY > &LYR2 > &LYR4 > &LYYMMDD > &MIN > &MON > &SEC > &SEQ > &SID > &SYSCLONE > &SYSNAME > &SYSPLEX > &SYSR1 > &SYSUID > &TIME > &WDAY > &YR2 > &YR4 > &YYMMDD > &SYSALVL > > > The comments in the quotes would be ignored. Same thing would happen if > you entered it from the console. > > Summary: > DD ALLOC=ACTIVE > DD ADD,SMS=( [DATA|D=[dataclas]][,MGMT|M=[mgmtclas]][,STOR|S=[storclas]) > DD NAME=some_data_set_mask_here > D D,O > > You can control your System Dump Datasets through ACS code or your can > specify the SMS classes you want Dumps to use in the DD ADD,SMS command. > > Try commands and determine what will work in your shop > > Lizette > > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] On > > Behalf Of suresh chacko > > Sent: Monday, June 23, 2014 6:55 AM > > To: [email protected] > > Subject: Re: COMMANDxx member > > > > Hi Kees, Lizette and Elardus > > > > Thanks for the replies. Elardus, Thanks for the SMS entry. > > > > Lizette, I have looked into the manual reference and did an internet > search too. > > Moreover looked into Redbook also. > > > > I have seen the below CD command in our COMMANDxx and so wanted to ask > > and confirm whether it is a valid code. So you mean this code should be > corrected > > as COM='CD SET,SDUMP,MAXSPACE=2048M'. > > > > > > COM='CD SET,SDUMP,MAXSPACE=2048M CHG DUMP VIRTUAL STOR TO > > 2G' > > > > I want to automate the dump allocation of dumpdatsets using SMS volumes > and > > issuance of DD ADD,VOL and CD SET,SDUMP commands from COMMANDxx > > to avoid partial dumps.. In any case IEA043I maxspace reached hit, CD > should be > > in effect. > > > > Kindly advise. > > Regards, > > Suresh > > > > > > > > On Mon, Jun 23, 2014 at 4:17 PM, Lizette Koehler < > [email protected]> > > wrote: > > > > > 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 > -- *SureshNc* ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
