Caveat: insert Daily Digest delay here... (you folx've probably already hashed this out and are onto other 'stuffs'.)
<quote> Note that logging-DDname is ignored if it is specified on the DD statement which describes a data set that is the target on the PARMDD keyword (see PARMDD parameter). </quote> Gil: What I read from the reference url is that EXEC ...,PARMDD=MYLOGDD along with SYMBOLS=(...,MYLOGDD) should fail. In other/my words, you can't pipe the logging results into the program via the Parm DD. Ex: failure (JCL error?) // EXEC PGM=,PARMDD=MYLOGDD //SYMBDD DD DATA,SYMBOLS=(...,MYLOGDD) //MYLOGDD DD ps. z/OS v1.12 not v2.1 here --------> signature = 6 lines follows <-------- Neil Duffee, Joe Sysprog, uOttawa, Ottawa, Ont, Canada telephone:1 613 562 5800 x4585 fax:1 613 562 5161 mailto:NDuffee of uOttawa.ca http:/ /aix1.uOttawa.ca/ ~nduffee “How *do* you plan for something like that?” Guardian Bob, Reboot “For every action, there is an equal and opposite criticism.” “Systems Programming: Guilty, until proven innocent” John Norgauer 2004 -----Original Message----- From: Paul Gilmartin [mailto:[email protected]] Sent: December 7, 2014 12:16 Subject: Re: PARMDD -- any one use yet? On Sun, 7 Dec 2014 11:20:40 -0500, Peter Relson wrote: > >I might well be thinking of something else, but for whatever reason I >was thinking that something might show what substitution is done for >PARMDD > Found it in: http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieab600/iea3b6_Syntax66.htm z/OS 2.1.0>z/OS MVS>z/OS MVS JCL Reference>DD statement>SYMBOLS parameter>Syntax But: ...logging-DDname Start of change Optional parameter that indicates a valid DD name for the data set to use for logging results of the symbol substitution. Rules for DD names are described in DDNAME parameter. Note that logging-DDname is ignored if it is specified on the DD statement which describes a data set that is the target on the PARMDD keyword (see PARMDD parameter). End of change ...ignored...! WTF!? Time for a Requirement? Either the substitution result should be logged in logging-DDname or it should appear in an informative message after the EXEC statement. I suppose one might add an IEBGENER step to show in logging-DDname the results of substitution in SYSUT1, followed by an other step using the passed SYSUT2 as PARMDD. No! No! No! Are there any constraints on attributes, etc. of logging-DDname? This was mentioned in a thread here, "SYSIN Symbol Resolution vs. LRECL" circa 2013-10-10. (I confess; I cloned the topic.) The Search facility in Knowledge Center sucks and/or I don't know how to use it. I found this only by searching a downloaded PDF of the JCL Reference for "PARMDD". Could I have done better? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
