Actually, this isn't due to any difference between ALLOCATE in batch and
ALLOCATE from TSO. Reason 0210 means that the dataset is unavailable
because it is allocated to another address space, most probably your
TSO session. You need to FREE FILE(NEWHFS) first; you could also logoff.
You don't need to do this for the batch job because it has already ended and
so freed the dataset; that is the equivalent of logging off TSO.
Bill
On Fri, 16 Mar 2007 14:59:49 -0400, Low, David <[EMAIL PROTECTED]> wrote:
>Hi Listers,
>
>Our system is z/os 1.6 with current maintenance.
>
>I'm struggling with a problem I'm hoping to fix before this weekend. I
>have a batch job executing IKJEFT1B that allocates an HFS dataset like
>so:
>
>ALLOCATE FILE(NEWHFS) NEW DATASET('OMVS.DAVE.TEST') DSNTYPE(HFS) +
> UNIT(3390) SPACE(1,1) CYLINDERS DIR(1)
>
>This works fine. When I run the same allocate command thru TSO or REXX
>I get an unmountable dataset. Mount command error: Errno=97x Dynamic
>allocation error; Reason=02100000
>
>Why is there a difference between ALLOCATE in batch vs. TSO?
>
>
>Dave Low
>Auto-Owners Insurance Co.
>
----------------------------------------------------------------------
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
