|
HEllo Tony, The job name for a batch job comes from the SBMJOB command--specifically the JOB keyword. This in turn defaults to *JOBD which causes the job to use the simple name of the job description specified on the JOBD keyword. This defaults to *USRPRF which causes the job description specified in the user profile of the user running SBMJOB to be used. These values can be overriden on the SBMJOB command. The system does not magically use the name of the program for a batch job (unless it is a Batch Immediate job started by spawn()). So either you have a shop naming convention that sets the job name to the program on the SBMJOB command, or you have different job descriptions for every batch job (hard to believe), or you are using spawn and don't know it. And yes, the Work Management guide explains this in detail. Regards, Simon Coulter. -------------------------------------------------------------------- FlyByNight Software AS/400 Technical Specialists http://www.flybynight.com.au/ Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ Fax: +61 3 9419 0175 mailto: shc@xxxxxxxxxxxxxxxxx \ / X ASCII Ribbon campaign against HTML E-Mail / \ --------------------------------------------------------------------
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.