MCH5601 while savobj in batch

[Guest.Visitor]

Hi. I have a problem. When our application try to savobj to *SAVF from CLP which SBMJOB running Dayend batch. We got the MCH5601 message. In our CLP we sure to CLRSAVF before SAVOBJ. I would like to know what should cause the system to sending this message. Becuase when we running the very same command on the same object in interactive mode it will never give us such a message. Even if the object cannot be saved because it was allocated by some other job. Thanks for every ideas.

[Guest.Visitor]

On Thursday, September 10, 1998, 11:03 PM, Panida wrote: Hi. I have a problem. When our application try to savobj to *SAVF from CLP which SBMJOB running Dayend batch. We got the MCH5601 message.....</p> <hr> Template value not valid for instruction. Cause . . . . . : The location of the value is template &1 with an offset to field in bytes &2, an offset in field in bits &3, a length of field of &4,and an instruction operand number of &5. The reason code is &6. If the reason code is X'0000', a reason code may not be available.</p> </P>It might help to post the message detail for MCH5601 and any messages from the joblog (check to make sure you are logging everything) Regards .....

[J.Pluta]

<font color=steelblue>On Thursday, September 10, 1998, 11:03 PM, Panida wrote: Hi. I have a problem. When our application try to savobj to *SAVF from CLP which SBMJOB running Dayend batch. We got the MCH5601 message.....</font><hr><font color=blue>On Friday, September 11, 1998, 09:29 AM, John Albert wrote: Template value not valid for instruction. Cause . . . . . : The location of the value is template &1 with an offset to field in bytes &2, an offset in field in bits &3, a length of field of &4,and an instruction operand number of &5. The reason code is &6. If the reason code is X'0000', a reason code may not be available.</p></P>It might help to post the message detail for MCH5601 and any messages from the joblog (check to make sure you are logging everything) </font><hr> In order to find the second level text for most of the system messages (e.g., MCHxxxx or CPFxxxx), simply do <pre>WRKMSGD MCHxxxx</pre>This will give you a subfile of messages from QCPFMSG (the system message file), nicely positioned right to your message. Take option 5 (Display Details), then option 30 (All of the above) and you'll see both first level and second level text. Incidentally, WRKMSGD MSGID(msgid) MSGF(QRPG/QRPGMSG) shows compiler errors, while WRKMSGD MSGID(msgid) MSGF(QSYS/QRPGMSGE) shows RPG runtime errors. Joe