|
At 02:10 27/09/98 -0700, you wrote: >I have a utility that can seems to behave in two different ways when >submitted using sbmjob and submitted using a scheduled job entry. >Moreover, in some instances the sbmjob does not generate the same >results as an interactive job. > > 1) When a submitted from an interactive job using submit job it >appears to work correctly accessing files in the correct manner >and producing the correct output. > > 2) When submitted from a scheduled job entry no output is produced. > >I know that when a sbmjob entry is evoked it copies the user environment >and authority well enough. > >The schedule job entry has QSECOFR as the user and contains a job >description that would mirror the environment of the interactive job (I >belive with the same library list). Is there a system value that would >be involved here or something else that may cause the schedule job entry >not the correct results. The program also uses QTEMP and shared folders. >What am I missing? > >Thanks in advance for any insight on this matter. > One suggestion - do the different user profiles have different default libraries ? I suggest you check out the user profiles and the job descriptions, and also the current library. The, using the paramters of the SBMJOB command as a guide, try and work out whetehr it would be getting submitted differently under each of the environments. Logging the job and checking the JOBLOG would also be a good move. Hope this helps Cheers +--- | 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.