|
John, You'll probably get a slew of different ways about this. This is what I would do; DCL VAR(&MSGDTA) TYPE(*CHAR) LEN(100) DCL VAR(&MSGID) TYPE(*CHAR) LEN(7) DCL VAR(&MSGF) TYPE(*CHAR) LEN(10) DCL VAR(&MSGFLIB) TYPE(*CHAR) LEN(10) DCL VAR(&JOB) TYPE(*CHAR) LEN(10) DCL VAR(&USER) TYPE(*CHAR) LEN(10) DCL VAR(&NBR) TYPE(*CHAR) LEN(6) SBMJOB CMD(....) JOB(....) RCVMSG MSGTYPE(*LAST) MSGDTA(&MSGDTA) MSGID(&MSGID) + MSGF(&MSGF) MSGFLIB(&MSGFLIB) CHGVAR VAR(&JOB) VALUE(%SST(&MSGDTA(1 10)) CHGVAR VAR(&USER) VALUE(%SST(&MSGDTA(11 10)) CHGVAR VAR(&NBR) VALUE(%SST(&MSGDTA(21 6)) Now you have all parts of the job name separated. I'm curious why you wanted the job number. All of my cl programs that do a sbmjob, right after the RCVMSG, I do the following; SNDPGMMSG MSGID(&MSGID) MSGF(&MSGFLIB/&MSGF) MSGDTA(&MSGDTA) which pushes the CPC1221 message back to the user. Hope this helps. Glenn Gundermann Ronald A. Chisholm Limited Toronto John Hall wrote: > After doing a sbmjob I need to capture the Job # of the submitted job. > > What is the best way to go about this ? > > TIA > > John Hall > Home Sales Co. > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.