Browse Prior Art Database

Activity Accounting for a JOB Entry Facility

IP.com Disclosure Number: IPCOM000042502D
Original Publication Date: 1984-May-01
Included in the Prior Art Database: 2005-Feb-03
Document File: 4 page(s) / 19K

Publishing Venue

IBM

Related People

Mahon, TA: AUTHOR

Abstract

Described is a method for operating a computing system including a network of peer-coupled nodes to provide a network activity accounting record. This is accomplished by (1) defining a network file as a data packet created by either JES2/NJE or VM/RSCS to include data contained between a network job header record and a network job trailer record (2) creating an activity accounting record for each network file received at and transmitted from a network job entry facility and a remote job entry facility, including receive records, receive-error records, send records, send-error records, and cancel records and (3) using activity accounting records to provide network activity accounting.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 23% of the total text.

Page 1 of 4

Activity Accounting for a JOB Entry Facility

Described is a method for operating a computing system including a network of peer-coupled nodes to provide a network activity accounting record. This is accomplished by (1) defining a network file as a data packet created by either JES2/NJE or VM/RSCS to include data contained between a network job header record and a network job trailer record (2) creating an activity accounting record for each network file received at and transmitted from a network job entry facility and a remote job entry facility, including receive records, receive-error records, send records, send-error records, and cancel records and (3) using activity accounting records to provide network activity accounting. Network Job Entry (NJE) is a feature of the IBM Job Entry System 2 (JES2) program that allows IBM Multiple Virtual System (MVS) Batch Jobs, Started Tasks and Time Sharing users to transfer packets of data from one system's spool volume to another system's spool volume. The systems are coupled together via a telecommunications link in a peer-to-peer session. Packets of data are then transferred via this medium. The destination system can be another MVS system with JES2/NJE or an IBM Virtual Machine (VM) system with the IBM Remote Spooling Communications Subsystem (RSCS) program product. The pooled packets of data that can be transferred are: Jobs, JCL and SYSIN, Sysout Data Sets, Messages, and Commands. Because differences between an MVS job or system output data set are not known to the VM/370 operating system and the VM operating system is not sensitive to the data contained within its spool data file, a network activity accounting record is herein defined that will provide statistics and tracking data for both JES2/NJE and VM/RSCS. This accounting record is compatible with both VM/370 files and MVS data sets, and the term "Network File" refers to the data packets created by either JES2/NJE or VM/RSCS. As a packet of data moves from node to node through the network, an audit trail is produced by the sending and receiving activity at each node. This idea is complicated by the fact that JES2 is job and data set oriented and RSCS is file oriented. A JES2 network data packet may consist of one or more system output data sets. JES2 creates a multi-file data packet for a job's output data set if the job has multiple output data sets whose characteristics are the same. Additionally, this collection of system output data sets must have the same destination.

When this multiple system output data packet reaches a VM/370 system, RSCS creates a separate spool file for each data set contained within the received network data packet . On the other hand, network data packets produced at a VM/370 node will consist of a single spool file . Therefore, the term "Network File" refers to the data contained between the Network Job Header Record and the Network Job Trailer Record. The purpose of the activity accounting record is...