On Tue, May 9, 2017 at 9:16 AM, Paul Gilmartin <
[email protected]> wrote:

> On 2017-05-09, at 01:42, venkat kulkarni wrote:
>
> > Yes. It's not.so I should code jesmsglg dd stmt as
> > //JESMSGLG dd sysout=a,free=close,spin=unalloc
> >
> > in my ims proc and then recycle ims and then issue
> > $t job,imsproc,spin,ddname=JESMSGLG
> > Command to spin JESMSGLG.
> >
> The JCL Ref. lists several DDNAMES not available for general use:
>     Special ddnames
>     The special data sets are identified by the following ddnames:
>         JOBLIB
>         STEPLIB
>         SYSABEND
>         SYSCHK
>         SYSCKEOV
>         SYSIN
>         SYSMDUMP
>         SYSUDUMP
>
> SDSF also shows me several (pseudo?) DDNAMEs such as
> JESJCL, JESYSMSG, and JESMSGLG.  What happens if the
> programmer attempts to override one of these, e.g. by
> directing it to a catalogued data set or a UNIX file?
>

​NCD - No Can Do. Those pseudo DDNAMEs cannot be directed to a non-SPOOL
data set or UNIX file. The only thing that I know could possibly be done is
to SPIN them off periodically (or aperiodically "as requested" via that $T
command) and then process the spun data, perhaps into a DSN or UNIX file
or, as we do, to a "remote" location via an LPR destination (which is a
Windows box driven from z/OS via MacKinney's JQP).



>
> The JCL Ref. indicates that they are available to the
> //*FORMAT PR statement.
>
> ("//*FORMAT PR" looks uncomfortably like a comment.  Is
> this a reserved comment?  Ugh!)
>

​this is a JES3 JECL (JEs Command Language) statement. And, yes, it _is_
also a regular JCL comment statement in a non-JES3 (i.e. JES2) environment.​



>
> -- gil
>
>
-- 
Advertising is a valuable economic factor because it is the cheapest way of
selling goods, particularly if the goods are worthless. -- Sinclair Lewis


Maranatha! <><
John McKown

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to