Submitting batch jobs: Difference between revisions

From Try-AS/400
Jump to navigation Jump to search
(IBM Link)
(+link)
Line 16: Line 16:


== Weblinks ==
== Weblinks ==
* [https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/cl/bchjob.htm BCHJOB (Batch Job)] description
* [https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/cl/bchjob.htm BCHJOB (Batch Job)] description, IBM
* [https://www.itjungle.com/2012/03/07/fhg030712-story02/ Interpreted CL Members], ITJungle


== Footnotes ==
== Footnotes ==

Revision as of 14:06, 29 March 2020

Qsicon Fixme.png This article isn't finished yet or needs to be revised. Please keep in mind that thus it may be incomplete.

Reason: Search for and add information about the JCL Clone OS/400 is using.

OS/400 shares some concepts with Mainframe operating systems, such as MVS (now z/OS). One of this possibilities is to submit Batch jobs to a remote machine[1][2].

Preparation

For the facility to work, first configure SNA Distribution Services.

Next, decide what the receiving machine should do when there are remote jobs being submitted:

  • Reject incoming requests,
  • File into the user's network file storage[3] (default),
  • Search the network job entry table what to do.
CHGNETA JOBACN(*REJECT|*FILE|*SEARCH)

Finally, provide entries to the Network Job Entry Table, what to do with Remote Jobs coming in.

WRKNETJOBE

Weblinks

Footnotes

  1. There's also a local-only equivalent called SBMDBJOB.
  2. SBMDBJOB is a somewhat extended version of the stock SBMJOB.
  3. To be seen in WRKNETF.