|
Mike, This is such a common question that one of us really should put it in the FAQ. Here is one of many explanations from the archives: http://archive.midrange.com/midrange-l/199809/msg01310.html John Taylor Canada ----- Original Message ----- From: "Wills, Mike N. (TC)" <MNWills@taylorcorp.com> To: <MIDRANGE-L@midrange.com> Sent: Wednesday, May 16, 2001 16:15 Subject: CL Problems > I have a RPG program that passes parameters to a CL program that retrieves > some job attributes, then submits another CL to the jobq which will build a > PDF file and put it on the IFS. The reason we do this is so if the PDF > creation crashes, it will not disrupt the job that called it. This CL is > called at the end of the job (we are being overly paranoid because some of > the reports do updates). My problem is this: > > Somehow between the RPG program and the last CL I get garbage in the field > name causing the last CL to crash. I am filling these fields in the RPG > program, but not completely (I might be using 20 bytes of the 50 byte > length). I don't want to make this smaller because the CL's are designed so > many different reports can be turned into PDF files. I am wondering how that > garbage can get in there. The data appears to be fine when it gets sent to > the first CL from the RPG program (thus why I posted here). :-) The only > ones effected are the ones that are quite long and not being completely > filled. OS version is V4R5. > > Thanks for any help. > > Mike Wills > +--- +--- | 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.