|
Laurin, Test and production are on one and the same machine; production is a library; pgmrs have test libraries; V4R4. The move process (which is only done when all users are off and all other production jobs are ended) moves the program object and source code from the test lib to production lib; if the pgm exists in production, it is forced to QRPLOBJ; the old source is also moved to Archive lib at this time. pgm obj in use appears to be one in production (even in wrkactjob-call stack) but in fact is not? The old program object exists nowhere else but in QRPLOBJ lib and seems to be the object running! We have only noticed this strange behavior since upgrading to v4r4 just a week before y2k. Could the force to QRPLOBJ be causing this? The programmer who created the move process is long gone so I cannot ask him why he included the force to QRPLOBJ- it seems to me that I could remove that logic without a hitch, but it is difficult to test in test area. Why might this logic have been included? Thanks! Allen L. Overeem Information Services St. Vincent Hospital Phone: (920) 431-3111 E-mail: aovereem@stvgb.org +--- | 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.