PINION, RICHARD W. wrote:

>From an SMS ACS perspective DSN=&&TEMP,DISP=(,DELETE) creates DSNTYPE=TEMP.

... and you will get something like this 
DSN=SYS17069.T155526.RA000.<jobname>.<DD>.**

Your SMS and ACS routines will place that dataset somewhere using defaults or 
some settings you or the system are using. 


>However, coding DSN=HLQ.MLQ.LLQ,DISP=(,DELETE) does not.  Is there a way to 
>treat them the same?

No, your ACS routines may place that DSN somewhere else in another DATACLAS, 
STORCLAS, etc. depending how you setup your ACS routines.

Only thing where both are treated the same - lifetime of that dataset. 
(a$$uming no PASS)

I have a look at DSNTYPE=TEMP, but AFAIK there is nothing where you can use 
DSNTYPE=TEMP in your SMS ACS routines.

But you could consider thinking about VIO?

Of course, I could be wrong about that DSNTYPE... (because we seldom use 
DSNTYPE=TEMP.)

Groete / Greetings
Elardus Engelbrecht

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

Reply via email to