|
The printer is easy. On the production machine, the printer file is defined as 80 bytes wide. On the test machine it is probably defined 132 or 198 or something. Run a query. Pick the correct printer file out of the job as it runs or out of the output queue then do chgprtf. I don't have a quick answer on the QM queries. Richard Jackson mailto:richardjackson@richardjackson.net http://www.richardjacksonltd.com Voice: 1 (303) 808-8058 Fax: 1 (303) 663-4325 -----Original Message----- From: owner-midrange-l@midrange.com [mailto:owner-midrange-l@midrange.com]On Behalf Of Dennis Munro Sent: Friday, September 01, 2000 8:53 AM To: 'Midrange E-Mail List' Subject: QM Query question AS/400 720 V4R4M0, current on all ptf's as of two weeks ago as a test machine. AS/400 S20 V4R4M0, not as current on ptf's as the test machine. Running BPCS 6.0.02 full client/server as an ERP package. I had 30 Query/400 queries I had converted to QM/400 queries on my test machine. They worked just fine on the test machine. I am not sure how I copied them from the test machine to the production machine but I probably copied the definitions into a work library, saved the work library to tape, restored the tape on the production machine, & then copied the sql & form definitions to the correct library. The queries all ran correctly on the test machine. I had to change all the queries on the production machine to point to the correct library & saved the definitions - but I never ran them. When I went to run them last night as part of month-end, they all aborted. Running the CL program through ISDB, I found out that the queries were all looking for the wrong data library, which only resides on the test machine. What did I miss (other than not trying them to make sure they ran which now makes me look pretty stupid) in this copying process? I then ran each one manually & they all worked, but not within my CL program???? At midnight, you sometimes don't really think to straight, especially after it being a 17 hour work day. The other kicker is after I ran the QM/400 queries manually, all the form definitions didn't work where I had a report wider than 80 columns. That all was working on the test machine. You get multiple reports based on the report width, ie. col.1-80 = report 1, col.81-160 = report 2, col.161-198 = report 3. What a mess. What am I forgetting or what did I do wrong? Frustrated & tired. Plus my wifes birthday & I will probably fall asleep while eating out with the kids. I should just go home right now & sleep & forget work. Dennis Dennis Munro Badger Mining Corporation dmunro@badgerminingcorp.com www.badgerminingcorp.com (920) 361-2388 +--- | 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.