Re: SMS PUZZLE

For your first IEBGENER:

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

For your second IEBGENER:

WHEN (&HLQ = &POOL_GDVX OR &DSN = &GDVX_DSN)
SET &STORCLAS = 'SCDEV'

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@xxxxxxxxxxx] On
Behalf Of willie bunter
Sent: Wednesday, April 30, 2008 12:15 PM
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" <barry.a.schwarz@xxxxxxxxxx> wrote:
...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.

________________________________



---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try
it now.

----------------------------------------------------------------------
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

----------------------------------------------------------------------
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: explicity coding for STORCLAS & DATACLAS
    ... The fact that you code an "SMS" parameter, such as STORCLAS and DATACLAS ... Depending on the code in each routine, ... requires analysis of ACS routines themselves. ...
    (bit.listserv.ibm-main)
  • Re: z/OS 1.8 upgrade
    ... Our only problem so far is with SMS & the LIKE parameter for PO or POE ... DATA CLASS WITH A DYNAMIC VOLUME COUNT GREATER THAN ONE, ALLOCATION ... using LIKE to allocate datasets in JCL or REXX/CLISTS. ... The intended recipient of this e-mail may only use, reproduce, disclose or distribute ...
    (bit.listserv.ibm-main)
  • RE: SMS question - sharing DASD but not SMS environment
    ... SMS question - sharing DASD but not SMS environment ... We would update SMS rules in every Lpar to indicate these ... The volumes used to transfer data from sysplex A to sysplex B are SMS ... Allocation of datasets containing data to be transfered is possible ...
    (bit.listserv.ibm-main)
  • Re: How to write out a variable length record?
    ... allocation then ... Or, although you're allocating a VB file, could SMS be creating a FB file ... "EXECIO 0 DISKW OUTHDR (FINIS" ...
    (comp.lang.rexx)
  • RE: explicity coding for STORCLAS & DATACLAS
    ... an SMS StorClass of 'NONSMS' to specifically NOT SMS manage a dataset ... explicity coding for STORCLAS & DATACLAS ... email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO Search ...
    (bit.listserv.ibm-main)