What can cause an IECTMS3 NS64 messages in my DB2 utility jobs?

Products

• CA 1 Flexible Storage

Issue/Introduction

 

Occasionally a DB2 job will the an IECTMS3 NOT SCRATCH(64) message.  Why and how do I resolve it?

 

 

 

Resolution

DB2 does a double open for some of its output files. You can use TMSXITF (or new with rel 14.0 TMODBL00 *.CTAPOPTN option member)  to allow this double open. CA-1 provides a skeleton for the module, and a usermod TMSXITF in CTAPJCL to help you code the exit. There is one line of code in the skeleton that must be commented out to activate the exit, (B NOACTION LET CA-1 RESUME PROCESSING 00207000). In the section of code labeled, DBLOPEN you should add logic to check for the DSN that DB2 would use or the job name, and then branch to ALLOW if you want to allow the double open to continue.