IBM Mainframe Forum

Hello,

I have submitted an XCOM JOB with FILEOPT=REPLACE option but getting the below given error
XCOMM0239E RC 0484 0000 ON DYNAMIC ALLOCATION


Initially i have submitted the job with FILEOPT=CREATE and submitted the job. After the file created in the receiving side changed the option to FILEOPT=REPLACE and submitted the job again. But the getting error XCOMM0239E RC 0484 0000 ON DYNAMIC ALLOCATION

Initially error displayed as Network error and later displayed as LOGIC ERROR.


I have tried MYXCOM pannel using REPLACE option and it is working fine.

Could you please advice me the course of action required so that i can submit the JCL using FILEOPT=REPLACE.

Please advice.


Thanks in advance.

There's no excuse for a vendor product to issue a message like this, when it is quite easy to create the same message that TSO would issue for the error. The error codes are documented in a relatively obscure place: MVS Authorized Assembler Services Guide. I must admit the official description (and, probably, the TSO message, too) is not all that helpful.

Request denied by one of the following: (dsname allocation)

° The operator
° The default policy specified in
SYS1.PARMLIB member ALLOCxx
° The installation exit specified in
SYS1.PARMLIB member EXITxx.

I would look in the JESMSGLG data set for the job for more clues. If that doesn't help, check other places as shown in the official description.

I have to admit this is not what my uninformed first guess would be, that the dataset was migrated to tape and the operator refused the recall request, or the DYNALLOC call explicitly rejected a recall; this is a different error code that I could not quickly locate.

There is no error message displayed in JESMSGLG
Updated that connection established
REquest processed sucessfully and

I have verified in TSO XCOM62 pannel the status remains ACTIVE for a long time and later turned into NETWORK Error and then changed to LOGIC error.

If the error is due to
Request denied by one of the following: (dsname allocation)

° The operator
° The default policy specified in
SYS1.PARMLIB member ALLOCxx
° The installation exit specified in
SYS1.PARMLIB member EXITxx.


what could be the course of action for that to remediate the effect

Please advice