Browse Prior Art Database

User Exit File Support Methods

IP.com Disclosure Number: IPCOM000076142D
Original Publication Date: 1972-Jan-01
Included in the Prior Art Database: 2005-Feb-24
Document File: 2 page(s) / 55K

Publishing Venue

IBM

Related People

Bendel, MP: AUTHOR [+3]

Abstract

This is a method for identifying user-exit data sets and placing the same into unique direct-access storage devices (DASD) files. User-exit data is data transmitted from a host data processing system [IBM OS/360 Remote Job Entry (RJE)] to a receiving system (IBM System/3 RJE), which is not directly or immediately used by the receiving system's printer or punch. All user-exit data is directed to a DASD file by the receiving system's control program (SCP). In this manner, data transmission line time can be reduced because data editing is performed on the data after it has been diverted to the DASD file. The system user edits the data read from the DASD file and sends it in the edited form to the printer or punch.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 100% of the total text.

Page 1 of 2

User Exit File Support Methods

This is a method for identifying user-exit data sets and placing the same into unique direct-access storage devices (DASD) files. User-exit data is data transmitted from a host data processing system [IBM OS/360 Remote Job Entry (RJE)] to a receiving system (IBM System/3 RJE), which is not directly or immediately used by the receiving system's printer or punch. All user-exit data is directed to a DASD file by the receiving system's control program (SCP). In this manner, data transmission line time can be reduced because data editing is performed on the data after it has been diverted to the DASD file. The system user edits the data read from the DASD file and sends it in the edited form to the printer or punch. The maximum number of unique user-exit data files for each RJE session is the maximum allowed for any job on the system.

The routine for determining record destination or user-exit data is shown in Fig. 1. This routine requires the user to specify the destination of each user-exit data set by DASD file name. The user specifies the file name prior to the user- exit data within the job stream as indicated by *** in Fig. 2. The user-exit file name does not have to come at the end of the job stream. If the file name is not specified before the user-exit data is returned, the SCP will stop and request the file name from the system operator as shown in Fig. 1.

1

Page 2 of 2

2

[This page contains 3 pictures or other non-text objects...