|
The LO indicator works very well. Just use the define the *PSSR subroutine and SDS to handle the errors. You'll find the error message ID & Text in the SDS as follows: 0064.00 * Program Exception Status Data Structure 0065.00 * 0066.00 IDSPGM SDS 0067.00 * 0068.00 I 1 10 @@PGM 0069.00 I 11 150@@ESTS 0070.00 I 21 28 @@ESTM 0071.00 I 40 42 @@ETYP 0072.00 I 43 46 @@EXC# 0073.00 => I 40 46 @@EMSG 0074.00 => I 91 170 @@EDTA 0075.00 I 244 256 @@JOB 0076.00 I 254 263 @@USER 0077.00 I 264 269 @@JOB# Then have your *PSSR process the appropriate errors. HTH, -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Jon A. Erickson - Viking Industries, Inc. jonerickson@vikingindustries.com -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -----Original Message----- From: Al Barsa, Jr. [SMTP:barsa2@ibm.net] Sent: Friday, January 09, 1998 6:42 AM To: MIDRANGE-L@midrange.com Subject: Re: QCMDEXC question At 07:01 AM 1/8/98 -0700, you wrote: >I am making a call to QCMDEXC from an RPG program. The >command being executed is CRTPF. I recieve a CPF7302 level >40 message 'File ABC not created in library XYZ. I need away to >monitor and ignore the message if the file already exists; I plan >to overwrite the previous file. > Two alternatives. You can use the LO indicator, which would indicate that the request given to QCMDEXC failed. It would not indicate why it failed, although you may not care. If you want some more sophisticated coding, you can do a call to a CL program, do a CHKOBJ for the file, and then create it if needed. Alternatively, if this is a QTEMP work file, where you needed a fresh copy, you could do a DLTF monitored with a CPF2105 if not found. The call to CL will not perform as well as the call to QCMDEXC, which may or may not be an issue. (Interactive use probably doesn't matter, once per record in a million record file would hurt.) Al Al Barsa, Jr. - Account for Midrange-L Barsa Consulting, LLC. 400 > 390 Phone: 914-251-9400 Fax: 914-251-9406 Private mail should be sent to barsa@ibm.net +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@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 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-2025 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.