|
Dan, Here you go.... 5769SS1 V4R4M0 990521 Message Description (Formatted Text) 2/07/00 16:32:51 Page 1 Message file . . . . . . . . . : TOOLMSGF Library . . . . . . . . . . . . : TOOLS Message IDs: USR8001 USR8001 Message . . . . : MSGKEY and MSGTYPE are mutually exclusive. If MSGKEY(*TYPE) is specified, you must give the MSGTYPE parameter a value other than *NONE. If a specific message key is specified in MSGKEY, you must specify MSGTYPE(*none). Severity . . . . . . . . . . . . . . . . . : SEV 0 Data to be dumped . . . . . . . . . . . . : DMPLST *JOB Message level . . . . . . . . . . . . . . : LVL 09/22/95 01 Alert option . . . . . . . . . . . . . . . : ALROPT *NO Log problem . . . . . . . . . . . . . . . : LOGPRB *NO Coded character set ID . . . . . . . . . . : CCSID 65535 * * * * * E N D O F L I S T I N G * * * * * 5769SS1 V4R4M0 990521 Message Description (Formatted Text) 2/07/00 16:32:51 Page 1 Message file . . . . . . . . . : TOOLMSGF Library . . . . . . . . . . . . : TOOLS Message IDs: USR8002 USR8002 Message . . . . : PGMSTKCNT(0) not allowed with PGMQ(*). If you specify PGMQ(*) to move program messages from the current program message queue, the PGMSTKCNT parameter must have a value greater than zero. Severity . . . . . . . . . . . . . . . . . : SEV 0 Data to be dumped . . . . . . . . . . . . : DMPLST *JOB Message level . . . . . . . . . . . . . . : LVL 09/22/95 01 Alert option . . . . . . . . . . . . . . . : ALROPT *NO Log problem . . . . . . . . . . . . . . . : LOGPRB *NO Coded character set ID . . . . . . . . . . : CCSID 65535 * * * * * E N D O F L I S T I N G * * * * * ----- Original Message ----- From: "Bale, Dan" <DBale@TFSA.Textron.com> To: <MIDRANGE-L@midrange.com> Sent: Monday, February 07, 2000 13:59 Subject: MOVPGMMSG utility from NEWS400 Oct.'93 > I am trying to implement a utility that requires the use of MOVPGMMSG from > the October '93 issue of News400. The MOVPGMMSG command source has a > comment that describes the parameters to use when compiling the command: > > /* PGM(*LIBL/QMHMOVPM) VLDCKR(MOVPGMMSGV) ALLOW(*IPGM *BPGM) MSGF(DEPMSGS) > */ > > It makes reference to a message file DEPMSGS. Two message ID's are > referenced in the source, USR8001 & USR8002. Since my copy of that issue is > either stashed far, far away in some box in the basement or, more likely, it > got trashed during a recent spring cleaning, can anyone resurrect the > contents of the message file or pass on what the article says about them? > > TIA! > > - Dan Bale > +--- > | 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.