Hi All,
We have just upgraded from V5.4 to V6.1 and have run into a problem with a program that does a sndpgmmsg of CPF1241. The date and time parameters are data types *UTCD and *UTCT. What should be used to populate those parameters when sending the message? Everything I've tried so far gives me strange date and time results. The string is SNDPGMMSG MSGID(CPF1241) MSGF(QSYS/QCPFMSG) MSGDTA(&JOBNAME *CAT &USER *CAT &JOBNBR *CAT &B8 *CAT &B8 *CAT &B10 *CAT &DATE *CAT &TIME) TOMSGQ(&USER) MSGTYPE(*INFO) where B8 and B10 are blank place holders.
Thanks for any help!
Carolyn
Software/Hardware used:
iSeries V6.1
ASKED:
February 4, 2011 2:33 PM
UPDATED:
February 24, 2011 5:39 PM
In general, the “objects” that are needed are 8-byte system date time stamps. You can review examples of those most easily by experimenting with the Convert Date and Time Format (QWCCVTDT) API and specifying {*DTS} as the input or output format depending on the direction you’re testing.
Apparently, these are also needing to be UTC values. You might review various ILE CEE* date/time APIs such as Get Universal Time Coordinated (CEEUTC) API and Get Offset from Universal Time Coordinated to Local Time (CEEUTCO) API.
That should at least get you going in a direction. I’ll see if I can track down an example, but it probably won’t be for a couple days at best.
Tom
BTW, you can use a temporary workaround by sending x’0000000000000000′ for the values — 8 bytes of binary zeros. That should give the “*N” value in any resulting text until you can put real values in.
Tom
Tom,
Thanks for your responses. According to IBM the best thing to do is create a copy of the message as it is in V5R4 in another message file add point the program to that message. Since this is in a 3rd party program that’s what I did. It wasn’t worth it to me to spend the time playing with the APIs.
Carolyn