|
Steve wrote >I have a CL (lets call it CL-A) that >calls another CL (lets call it CL-B - >which is proprietary, and I don't >have source code for). > >If I run CL-B as a stand alone, >if invalid information is >entered in one of the prompts, when >enter is pressed the CL will use >a SNDPGMMSG command, and >on the program status line, it >will show a message showing >something like "outq not valid", >or whatever the problem was. > >When I now run CL-A, which calls CL-B, >if the same invalid information is >entered, you do not see the message >in the program status line. A message subfile will do what you want. A R MSGSFL SFL A SFLMSGRCD(22) A WMSGK SFLMSGKEY A WPGMQ SFLPGMQ A R MSGSFLC SFLCTL(MSGSFL) A SFLDSP A SFLINZ A SFLPAG(0002) A SFLSIZ(0004) A WPGMQ SFLPGMQ in your CL, do a SNDF MSGSFLC --buck
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.