MVSFORUMS.com

[Arun]

Hi all,
One of my DB2 job (which does REORG, RUNSTAT AND COPY TABLESPACE), is abending with the following return code
"SYSTEM COMPLETION CODE=7FC REASON CODE=00000004"
It has the following mesage in the sysout.
"DSNUGBAC - UTILITY BATCH MEMORY EXECUTION ABENDED, REASON=X'07FC' "

any pointers ?? y this is happening and how to solve.

[bablack]

In general, abends are named for the SVC that they result from. 7FC would be from SVC X'FC" (252). SVC numbers below 128 are for IBM SVCs, but SVCs above 127 are user-assigned, which means they are usually used by third-party software.

Third-party software which uses SVCs usually lets the customer assign the SVC during installation, to avoid collisions between software products.

One product which does this is the CA-1 tape management system which uses two SVCs. 252 might be one of them in your shop.

If you job used tape, then the abend could be
7XX - a DISP=MOD tape was rejected
7YY - the CA-1 AUDIT file is full

Check the joblog to see if any CA-1 messages were produced. If not, then it may be from some other third-party software product.

Bruce Black
_________________
Bruce A. Black
Senior Software Developer
Innovation Data Processing

[Bithead]

You may also want to check for APF authorization on the load library.

[bablack]

what makes you suspect an authorizaiton problem?

Bruce
_________________
Bruce A. Black
Senior Software Developer
Innovation Data Processing

[Arun]

Thatz an excellent pointer bablack
I'm getting the following messages
"IEFTMS50 7XX- 04" and
"IEFTMS50 ***** CA-1 ABEND,EX,04 *****"

and i'm using a tape with 'MOD' disp and has the following parameters in the definition
DISP=(MOD,CATLG),
UNIT=DISK,
SPACE=(CYL,(200,200),RLSE,,ROUND)

There is an another message "IECTMS3 4168,444780,IS NOT SCRTCH (64)" which says, the tape volume the file trying to use is not scratched and is not in the reusable state.This job is a part of the regular weekly job, runninig for years with no problem, with the same DCB parameter for the tape. I'm surprised why it should happen as of sudden.
Is there anything that can be done, to complete the job successfully and to avoid happeninig in future.

[bablack]

Although your DD has UNIT=DISK, it is obviously going to tape. I presume you also have a DSN= parm and do NOT have a VOL= parm. In that case, the system will lookup the dataset name in the catalog and mount the volume recorded there and try to MOD onto it.

That IECTMS3 64 message indicates you are trying to "recreate a dataset with DISP=NEW", which doesn't seem to be true.

I would do 2 things:
1-check a previous execution of the job to see if it used tape; perhaps someone recataloged this datsaet to tape by accident
2- check CA-1 for the status of tape 444780. make sure it has the right dataset name on it, is not scratch, and has records in it. If not, perhaps someone scratched or reused your tape by accident. Or maybe it expired naturally and was reused.
_________________
Bruce A. Black
Senior Software Developer
Innovation Data Processing

[Arun]

You are right bablack.
File as per definition, it has to write to disk, but for some reason, the SMG group, started pointing that to the Tape. Thatz why it was writing to tape, though it is defined to write in a disk.
We have asked to uncatlog the file, so that it will create the file in different volume, as the Disp parameters defined as 'MOD'. it is expected to create a new file in the next run.