Thank you thats what I thought, I will give it try.
 
S
Richard,

Thank you thats what I thought, I will give it try.
 
Scott J Ford
 




________________________________
From: Richard L Peurifoy <[email protected]>
To: [email protected]
Sent: Wed, June 15, 2011 1:38:48 PM
Subject: Re: CAMLST MACRO question

On 6/15/2011 12:07 PM, Scott Ford wrote:
> I have a quick process / CAMLST macro question after readi
> Hi All:
>
> I have a quick process / CAMLST macro question after reading thru the 
DFHsmsdfp
> manual.
> My situation is that I want to find a catalog QSAM file and then delete 
> it..do 
>I
> assume I do the following in Assembler:
>
> 1.  CAMLST LOCATE INDAB      where INDAB is the CAMLST macro with the dsname 
>and
> storage area
> 2.  if this macro returns a R15 = 0 , means it was found
> 3.  CAMLST CATALOG REMOVE  where REMOVE ponts to CAMLST UNCAT,DSNAME
> 4  if this macro returns a R15=0 , means it was uncataloged
> 5.  CAMLST SCRATCH ABC  where ABC is CAMLST SCRATCH,DSNAME,,VOLIST,,OVRD
>
> If this process is correct, how do I know where the dsname 'lives', which 
>volume
> ?  or is that returned in the LOCATE...

LOCATE if successful will return a volume list (remember it might be
a multi-volume dataset). I think LOCATE may be limited in how many
volumes it will return, the return area is only 265 bytes.

I think the volume list starts with a 2 byte count of volumes
followed by 12 bytes entries (4 bytes device type, 6 bytes serial,
2 bytes sequence number).

--
Richard

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] 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 [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to