|
If you need to retrieve the job description from your currently running
job you can do this:
https://www.ibm.com/docs/en/i/7.5?topic=services-job-info-table-function
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
http://www.dekko.com
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Marc Rauzier
Sent: Wednesday, November 9, 2022 4:34 AM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: Job Description for job submitted by Subsystem Autostart Job
CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know
the content is safe.
Le 08/11/2022 à 23:59, Vinay Gavankar a écrit :
Hi,Hello
description
I have an Autostart job defined on a Subsystem with a specific job
description. The job description has Routing Data to call a specific
program. This program submits other jobs when the Subsystem starts.
Currently, the jobs are being submitted with a 'hard-coded' job
in the SBMJOB command (same jobd as in the AJE). The ask is to remove theused
hardcoding, but still somehow submit the job with the Job Description
in AJE.the
First question is, if I were to omit the JOBD parameter on the SBMJOB
command in the start-up program, which jobd will be used for submitting
job?
Default is *USRPRF, which means the job description of the user profile
submitting job.
Is there any way to retrieve the JobD that was used to submit thestart-up
job or that is on AJE?
This AUTOSTART_JOB_INFO SQL view might help. Checkout
https://www.ibm.com/support/pages/node/6156117.
TIA--
Vinay
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.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.