Re: SMS PUZZLE

This is your FILTLIST statement:

FILTLIST VOL_NONSMS INCLUDE(%IPL*,%RES*,%PGE*,%PGL*,%CE*,%LI*,
SPL*,GMAIL%,'REF=NS',%L1*,%L2*,%M1*,%M2*,GPROV%,VEB4*,VEB5*)

Notice the first entry. Now look at the VOLSER you specified in the
JCL. Does that VOLSER match? The % matches the S; the IPL matches the
IPL; the * matches the AB. So the VOLSER does match the FILTLIST.

Here is your WHEN clause:

WHEN (&ANYVOL = &VOL_NONSMS OR &HLQ = &HLQ_NONSMS)
SET &STORCLAS = ''

YOU TOLD THE SYSTEM TO MAKE THE DATASET NON-MANAGED. The system did
exactly what you told it. What were you expecting? What part of
evaluating this caused you confusion?

-----Original Message-----
From: willie bunter [mailto:snip]
Sent: Wednesday, April 30, 2008 9:15 AM
To: IBM-MAIN@xxxxxxxxxxx
Subject: Re: SMS PUZZLE

Barry,

To confirm, the ACS that I posted is the current version. I am still
unable to figure out which WHEN condition is kicking in. When I coded
the unit & volser, the dsn was allocated on the non-SMS pack. When I
coded the only unit=3390, SMS directed the dsn to a SMS managed dasd.

Below is my jcl that I used to test the allocation :

//STEP1 EXEC PGM=IEBGENER
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//SYSUT1 DD DUMMY
//SYSUT2 DD DSN=TEST.TESTING.UNI3390.VOLSER,UNIT=3390,
// VOL=SER=SIPLAB,
// DISP=(,CATLG,DELETE),SPACE=(TRK,(1,1))
//SYSPRINT DD SYSOUT=*

//STEP1 EXEC PGM=IEBGENER
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//SYSUT1 DD DUMMY
//SYSUT2 DD DSN=TEST.TESTING.UNI3390,UNIT=3390,
// DISP=(,CATLG,DELETE),SPACE=(TRK,(1,1))
//SYSPRINT DD SYSOUT=*
//*

If you can think of something that I should try, please let me know.

Thanks again.

"Schwarz, Barry A"
...You need to look at the allocation request (probably in the JCL)
and determine which WHEN is the first to evaluate TRUE. That will tell
you why the dataset is or is not SMS managed. It would also be worth
checking if the ACS routine you posted is the one in actual use. If you
still cannot resolve the problem, post the complete DD statement or
other source of the allocation.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

.

Relevant Pages

  • Re: CA ESD files
    ... modify all the example JCL to the actual volser in the VTS. ... Don't you typically have to modify at least couple of jobs when you ... I have a edit macro that I just change every time I install a product ...
    (bit.listserv.ibm-main)
  • Re: SMS PUZZLE
    ... You need to continue this discussion in IBM-MAIN. ... you claim that that the allocation ... The next test checks the VOLSER. ... out to non-SMS disks start with the HLQ TEST.CNSA, ...
    (bit.listserv.ibm-main)
  • Re: VTOC audit trail - init of new dasd volumes
    ... generator that, in addition to building the JCL, updates an audit file. ... Lots of us have REXX that generates DASD INIT JCL. ... And doesn't show any volser details. ...
    (bit.listserv.ibm-main)
  • Re: Copy uncataloged datasets on tape.
    ... The datasets are still in uncataloged state. ... accessing the dataset using the VOLSER but it is still unaccessible. ... need a JCL which would help me catalog those datasets or a JCL to copy ... This is a tape dataset related question for mainframes. ...
    (comp.unix.questions)