The previous step deletes earlier file , while later it is not allocating the same dsn.

Code has below specs:
-****************************************************************
-SET &ALLOCX2E = 'PP0TDSMI.LSEQ.TDS0207.EXPDEFRD.S'|&DATE_RUN;
DYNAM FREE DDNAME HOLD2E
DYNAM DELETE &ALLOCX2E
DYNAM ALLOC FILE HOLD2E DA &ALLOCX2E -
SPACE 30,10 CYLINDER NEW

while when running it is not picking the last character of date , which should be 160822.
But it is picking the below and giving error.
[I]ERROR AT OR NEAR LINE 394 IN PROCEDURE TDS0207 FOCEXEC FOC855) UNABLE TO LOCATE DATASET PP0TDSMI.LSEQ.TDS0207.EXPDEFRD.S16082 #026-08

This message has been edited. Last edited by: <Emily McAllister>,

Can you try using a || instead of a |, just in case there are spaces in the variable ?

using || is not helping ...

Does run date have the full date ?

also try -TYPEing &ALLOCX2E and see if its correct there. i.e. is it the concat line or something else

I tried to run this in test , there it is picking the correct date but the error is same.


DYNAM DELETE TDSMI.TEST.TDS0207.EXPDEFRD.S160822
ERROR AT OR NEAR LINE 394 IN PROCEDURE JULY0207FOCEXEC
(FOC855) UNABLE TO LOCATE DATASET TDSMI.TEST.TDS0207.EXPDEFRD.S160822,
#026-08

Why it is not finding this Dataset, I can see it when browsing... (through 3.4) ?

I will try the TYPYing &ALLOCX2E though.

TYPEin &ALLOCX2E is showing as below:

* DATE RUN : 160822
* ALLOCATED X2E : TDSMI.TEST.TDS0207.EXPDEFRD.S160822
**************************

So seems no problem with the date_run value.
Need some more clue to identify.

I suspect it's a (harmless) warning that the DELETE failed.

If the previous allocation of HOLD2E was a temp dataset, then after the FREE the dsn disappears and there is nothing left to delete.

As to the truncated dsn in the error msg, that may just be a space limitation in the message generator. What does the dsn look like in the echo of the dynam delete statement?