|
Is the batch user ID the same as the interactive test user ID? If the user is the same, then there is a difference between how a job runs in batch versus how it runs in interactive. The only thing that I can think of is that the interactive jobs acquires different authority after start up and that accounts for the difference. If you have a specific example, write a little program using just that example and try it in each case. Log on as some third user. I assume that you have looked for PTFs and so forth? Cumes don't contain all the PTFs. Richard Jackson mailto:richardjackson@richardjackson.net 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 Ted Barry Sent: Thursday, August 17, 2000 10:14 AM To: MIDRANGE-L@midrange.com Subject: RE: CHKOBJ Broken Under V4R3? Repost since meltdown... Right! >>> "Richard Jackson" <richardjackson@richardjackson.net> 07/14/00 07:22pm >>> The program running the CHKOBJ doesn't adopt authority, right? Richard Jackson mailto:richardjackson@richardjackson.net 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 Ted Barry Sent: Monday, August 14, 2000 4:07 PM To: MIDRANGE-L@midrange.com Subject: CHKOBJ Broken Under V4R3? Ever since going to V4R3 we've been having trouble with a particular job in the job scheduler. This job checks for specific authorities against an object and if they don't exist for certain profiles, an adopted program is run and grants the authorities. I'm doing the following: CHKOBJ OBJ(&LIB/&FILE) OBJTYPE(*FILE) AUT(*OBJMGT) MONMSG MSGID(CPF9802) EXEC(DO) blah dee, blah dee, blah ENDDO This has been checked interactively and the user isn't authorized, but when it runs in the CL, we never get to "blah dee, blah dee, blah". +--- | 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 +--- +--- | 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-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.