> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-comun-z-os-en/interfaz-generica-de-aplicacion/anexo-b.-programas-y-exit-de-usuario/autooperador-batch.md). # Batch auto-operator ## General description A user program has been created, which can be included in profiles or called from the user programs themselves, and which allows, among other things, linking with the entity schedulers and launching JCLs or procedures. As a result of incorporating this new functionality, the step area to the user program in the case of A7I has been modified, so that the presentation session is passed instead of the transmission session. That program is ZTBGBUOP, which reads a file containing the request list, called installation prefix-ZTBGFUSU, flat 200-byte file. ## Input/output elements Communication area: passed by the invoking Editran programs. Its content was specified in the user program. File used in the program (ZTBGFUSU), created by the user, whose format is specified below: ```cobol 01 REG-FUSU. 03 REG-200-FUSU PIC X(200). 03 REG-CGO-A7I-FUSU REDEFINES REG-200-FUSU. 05 EMI-REC-FUSU PIC X(3). 05 FILLER PIC X. 05 CGOS-FUSU OCCURS 36. 10 CGO-A7I-FUSU PIC X(3). 10 FILLER PIC X. 05 FILLER PIC X(52). 03 REG-PETICIONES-FUSU REDEFINES REG-200-FUSU. 05 PETICION-E-FUSU PIC X(40). 05 FILLER REDEFINES PETICION-E-FUSU. 10 FUNCION-E-FUSU PIC X(02). 10 SESION-PRES-E-FUSU. 15 LOCAL-E-FUSU PIC X(9). 15 REMOTO-E-FUSU PIC X(9). 15 APLICACION-E-FUSU PIC X(6). 10 REFERENCIA-A7I-E-FUSU. 15 EMI-REC-A7I-E-FUSU PIC X. 15 CGO-A7I-E-FUSU PIC X(03). 10 FILLER PIC X(10). 05 PETICION-S-FUSU PIC X(160). 05 FILLER REDEFINES PETICION-S-FUSU. 10 FUNCION-S-FUSU PIC X(02). 10 SESION-PRES-S-FUSU. 15 LOCAL-S-FUSU PIC X(9). 15 REMOTO-S-FUSU PIC X(9). 15 APLICACION-S-FUSU PIC X(6). 10 HORA-INI-FUSU PIC X(4). 10 HORA-FIN-FUSU PIC X(4). 10 COD-RET-S-FUSU PIC 9(4). 10 FILLER REDEFINES COD-RET-S-FUSU. 15 NRO-REINT-FUSU PIC 9(4). 10 NFUNCION-S-FUSU PIC X(02). 10 UBICACION-S-FUSU PIC X(44). 10 FILLER REDEFINES UBICACION-S-FUSU. 15 TIEMPO-WAIT-FUSU PIC 9(8). 15 FILLER PIC X(36). 10 FILLER PIC X(76). ```


Level	Name	Length	Type	Description
1	Record of processable A7I codes.	200	Alphan.	Record of A7I reference codes that will be processed by the program. Several records of this type can be defined.
2	A7I type	3	Alphan.	‘EMI’. The codes in the record are emission codes ‘REC’ The codes in the record are reception codes.
2	Filler	1	Alphan.	Separation space
2	A7I codes table	144	Alphan.	A7I emission or reception references table OCCURS 36 (the last 2 octets are ignored)
3	A7I reference	3	No.	A7I reference
3	Filler	1	Alphan.	Separation space
2	Filler	52	Alphan.	Reserve area
1	Input-action, output-action record	200	Alphan.	Record where the causing action and the action to be taken are entered.
2	Causing action	40	Alphan.	Data area reserved for the causing action
3	Causing function	2	No.	Spaces: any action 01: Emission load 02: After emission 03: Presentation emission 05: Emission exception (interrupt emission) 06: Reception initialization 07: After reception 08: Presentation reception 09: Reception exception (interrupt reception)
3	Presentation session Causing	24	Alphan.	Presentation session code.
4	Presentation origin Causing	9	Alphan.	Source code of the causing presentation session Spaces: Any code is valid
4	Causing presentation destination	9	Alphan.	Destination code of the causing presentation session Spaces: Any code is valid
4	Presentation application Causing	6	Alphan.	Causing presentation application Spaces: Any code is valid
3	A7I reference Causing	4	Alphan.	A7I reference specific to be processed in the request (in the case of function 05 and 09). Spaces: Searched in the A7I record.
4	A7I ref. type Causing	1	Alphan.	A7I reference type (E: Emission, R: Reception).
4	A7I ref. code Causing	3	No.	A7I reference code.
3	Filler	10	Alphan.	Area reserved for the causing request
2	Action to take	160	Alphan.	Data area reserved for the action to take
3	Action-to-take function	2	No.	01: Emission load 02: After emission 03: Presentation emission 05: Emission exception (interrupt emission) 06: Reception initialization 07: After reception 08: Presentation reception 09: Reception exception (interrupt reception) 21: Return the return code 22: Submit procedure 23: Submit JCL 24: Control of number of retries in A7I 25: Wait for a time (WAIT), before continuing with what is specified.
3	Action-to-take presentation session	24	Alphan.	Presentation session code
4	Action-to-take source presentation	9	Alphan.	Source code of the presentation session of the action to take.
4	Action-to-take destination presentation	9	Alphan.	Destination of the presentation session of the action to take.
4	Action-to-take presentation application	6	Alphan.	Presentation application of the action to take.
3	Action-to-take start time	4	No.	Spaces or zeros: Do not validate start time. HHMM: It will be validated that the action to take is after the action start time
3	Action-to-take end time	4	No.	Spaces or zeros: Do not validate end time HHMM: It will be validated that the action to take is before the action end time
3	Action-to-take return code	4	No.	Return code that the program will return. It is only used if the action to take is equal to 21
3	REDEFINITION
4	Number of retries	4	No.	Number of retries (0001-9999). It is only used if the action to take is equal to 24 and it is an A7I
3	New function to take	2	No.	New action to take (see action to take), if action to take = 22. The user can set it to whatever value they want for their procedure
3	Location of the JCL of the action to take	44	Alphan.	Field with variables to execute a JCL-procedure (as specified in the corresponding table). It is only used if the action to take is equal to 22 or 23. If the action is 23, only the name of the procedure will be entered, which may be a variable name (up to 8 positions)
3	REDEFINITION
4	Wait time	8	No.	Wait or WAIT time before continuing (HHMMSSDC). It is only used if the action to take is equal to 25 and it is an A7I
4	Filler	36
3	Filler	86	Alphan.	Area reserved for the causing request

Within the location, the job name will be 8 characters. If not, a character is generated at the end, which will be the digit of the incoming request. To provide the location of the procedure or the JCL, the rules for putting variable pointers used to choose the reception application file name will be followed, specifically: Allowed % variables. If the input variable does not contain a valid value, the default value is applied (since there are more allowed variables, ZTBGBUOP must ensure that only those specified below are present):


Var	Meaning	Valid value.	Default value.
%Y	Last digit of the year
%A	Last two digits of the year (yy)
%M	Month in two digits (mm)
%X	Month in one character (1,2,3,4,5,6,7,8,9,O,N,D)
%D	Day of the month (dd)
%H	Time (hhmmss)
%R	The last 7 characters of the remote endpoint code	Different from spaces or x’00’	Zeros
%P	Application code	Different from spaces or x’00’	Zeros

## Call conditions The program runs when required by the procedure main program or by the already created user program, once the complete treatment of the process has finished. The program's input conditions vary depending on the process: * Before output: It is invoked after loading the output buffers, regardless of whether it succeeded or not (result code = 0 or # 0). * Before reception: After initializing the buffers. * After output: At the end of the process of the last transmission session. * After reception: After the data download that is triggered when the last transmission session ends. * Exception: The program is invoked in any case. An example is attached below in which the contents of the ZTBGFUSU file are specified: ``` EMI-010-020-021-022-023-024-150 REC-030-040-050-060-070-080-090 09000099980000099940PRUEBA ----------08000099980000099940PRUEBA00002359 E230----------01000099980000099940PARAMI10301130 09 000099960PRUEBAR100----------21 0029 01000099980000099940PRUEBXR100----------22000099980000099940PARAMI 03J%R 01000099980000099940PRUEBAR100----------23000099980000099940PARAMI KI.L%A(J%R) ``` The meaning would be: * Entry 01: Emission A7I reference codes, which will be processed by the program. * Entry 02: Reception A7I reference codes, which will be processed by the program. * Entry 03: When a reception A7I of the described session arrives, 000099980000099940PRUEBA, if the A7I code belongs to those in entry 02, the reception of the presentation (function 08) of said session is requested. * Entry 04: When any message arrives that has an emission A7I with code E230 (even if it is not in entry 02), a pre-emission will be launched, as long as the system time is between 10:30 and 11:30. * Entry 05: When an emission load of the A7I reception session with remote-application reference R100 described above arrives, with any of the multienvironment codes of my entity, the job that is being executed will end with return code 29. * Entry 06: When a request for an emission load of the session 000099980000099940PRUEBX arrives, a procedure called J0099940 will be generated. The following will be passed as PARM: ORIGEN='A', FUNCION='03', L0='alias of the local subenvironment', L01='000098', L2='980', R1='000094', R2='980', AP='PARAMI'. * Entry 07: When a request for an emission load of the session 000099980000099940PRUEBA arrives, a JCL found in the KI.LPRUEBA library will be generated, and it will be called J0099940. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-comun-z-os-en/interfaz-generica-de-aplicacion/anexo-b.-programas-y-exit-de-usuario/autooperador-batch.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.