> 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-ims-en/utilidades-ims/borrado-tampon-emisor-receptor/informe-preliminar-de-la-bd-de-emision-recepcion.md). # Preliminary Report of the Send/Receive DB A BMP process will read the database looking for those sessions that match the session template and whose load or update date is earlier than or equal to a given date. **Input** The input is: * A search date, * A search session, with zeros for generic selection of environments, remotes and applications, * A parameter to search by creation date or modification date, in the case of output, and by last confirmation date in the case of reception. A session load starts on the 'creation date' and ends on the 'last insertion date' or 'modification date', which is normally the same. With cumulative loading, the process starts on a date and, on successive days, if there is no transmission, new files are added. The difference between creation and modification date can be significant. It should be noted that the last insertion date refers only to the loading process; under no circumstances is it modified by the transmission or by a transmission attempt. For sessions with normal loading, this parameter is irrelevant, and it is recommended to use the modification date. For sessions with cumulative loading, it is advisable to compare the report by creation date with the one by modification date. A parameter indicating whether it is to be done on the output or reception buffer. The process is launched with JCL ZTBGJBO1. It runs in a BMP with read option on the buffer that does not execute CHKP-POINT. If there are several output/reception databases, the process will be repeated for each database, providing the appropriate PSB in each case. This process does not read the entire database but only the buffer control records, one per session. For this reason, it may not correctly report a given session if the record found is not the zero control record but some isolated record from a failed load or deletion **OUTPUT** The output is a listing, sorted by session, with information on: * The creation / modification / confirmation date, as requested, of the load, * The number of buffer records, * The session description and the presentation session. Certain fields will appear in the report as “??” when there are no Editran session records or control records. A list of the sessions found is also generated. Any detected error will be handled through the Editran/G Log. ## ZTBGJBO1. In this example, a report by creation date is requested for all INDRA IMS sessions against Indra CICS that were loaded up to 31/11/2002. ```cobol EDIT KI.EGDI.ZTBG.JCLS(ZTBGJBO1) - 01.39 Columns 00001 00072 Command ===> Scroll ===> CSR //KI0E8A2B JOB (EGDC,KIT,,99),'ZTBGJBO1',MSGCLASS=H,CLASS=A, // NOTIFY=&SYSUID //LIBPROC JCLLIB ORDER=IMSP.PROCLIB //*-------------------------------------------------------------------- //* DELETION OF THE OUTPUT/RECEPTION DB. STEP 1 //* SELECTION OF SESSIONS LOADED UP TO A DATE //* GENERATES SESSION LIST ZTBGFSES //* RUN AFTER ZTBGJBO2 AND ZTBGJPET //*--------------------------------------------------------------------- //*JCL CARD FORMAT //* //*DD/MM/YYYY-LLLLLLLLL-RRRRRRRRR-AAAAAA-T-X //*DD/MM/YYYY --------------> DATE TO SELECT //* //*LLLLLLLLL-RRRRRRRRR-AAAAAA SESSIONS TO SEARCH (LOCAL REMOTE APPLICATION) //* ZEROS OR SPACES FOR GENERIC SELECTION //* IN EACH FIELD //*T -----------------------> TYPE OF DATE TO SEARCH //* 'C' BUFFER CREATION DATE //* 'M' MODIFICATION DATE //* (LAST INSERTION DATE - OUTPUT) //* WITH CUMULATIVE LOADS USE //* 'C' TO SEARCH THE FIRST LOAD //* 'M' FOR THE LAST //* WITH ORDINARY LOADS USE 'C' OR 'M' //* INTERCHANGEABLY //* (LAST CONFIRMATION DATE - RECEPTION) //*X -----------------------> 'E' OUTPUT //* 'R' RECEPTION //*--------------------------------------------------------------------- //ZTBGEBO1 EXEC IMSBATCH,MBR=ZTBGEBO1,PSB=ZTBGEBO1,REGION=0M //STEPLIB DD DSN=KI.EGDI.LOAD,DISP=SHR //SYSOUT DD SYSOUT=* //CEEDUMP DD SYSOUT=* //ZTBGFLOG DD SYSOUT=* //ZTBGFLIS DD SYSOUT=* //ZTBGFMSJ DD SYSOUT=* //ZTBGFPRI DD SYSOUT=*,DCB=(BLKSIZE=105) //ZTBGFINF DD SYSOUT=* //*SEQUENTIAL OF 80 //ZTBGFSES DD DSN=KI.EGDI.ZTBG.ZTBGFSES,DISP=SHR //SYSIN DD * 31/05/2026-000099980-000099940- -C-E *to select all sessions *31/05/2026- - - -C-E ****** **************************** Bottom of Data **************************** ``` The ZTBGFSES file will contain the list of sessions found. ## Listing. The execution generates the following report. ``` DATE : 23/06/2026 O U T P U T D A T A B A S E R E P O R T (ZTBPDEMD) -EDITRAN- PAGE : 1 TIME : 13:26:15 CREATION DATE : 31/11/2002 LOCAL : 000099980 REMOTE : 000099940 APPLICATION : DATE RECORDS LOCAL REMOTE APPLICA PRESEN LOCAL NAME REMOTE NAME APPL. NAME ---------- ------------ --------- --------- ------ ------ --------------- --------------- --------------- 2026/05/29 5 000099980 000099940 CE9994 CE9994 INDRA IMS CICSSITD CHECK RECEIPT 2026/06/01 5 000099980 000099940 CE9998 CE9998 INDRA IMS INDRA CICS CHEQUE OUTPUT 2026/05/30 5 000099980 000099940 EE9994 EE9994 INDRA IMS ZTINDRA CICSSIT CASH RECEIPT 2026/02/14 4 000099980 000099940 ER9998 ER9998 INDRA IMS ZTINDRA CICSSIT OUTPUT RESEND 2026/04/16 9 000099980 000099940 OR9998 OR9998 INDRA IMS 2026/01/28 2.352 000099980 000099940 PRUEB1 PRUEBA INDRA IMS 2026/05/26 2.756 000099980 000099940 PRUMJ1 PRUMJG INDRA IMS 2026/01/25 5 000099980 000099940 TE9994 TE9994 INDRA IMS ZTINDRA CICSSIT EXCEPT. T RECEIPT 2026/05/26 5 000099980 000099940 VR9994 VR9994 INDRA IMS CICS TEST REC.CHE.SPE.RE ------------------------ -------------------------- TOTAL REC: 5.146 TOTAL SESSIONS: 09 (1) NO CONTROL RECORD (2) EDITRAN/G SESSION DOES NOT EXIST (3) EDITRAN/P SESSION DOES NOT EXIST *** E N D O F L I S T I N G *** ``` This listing can be used, by sorting on the appropriate column, to select the sessions with the most records or the oldest dates. ## ZTBGFSES Session List. The generated session list is as follows. ``` 000099980-000099940-CE9994-N-CE9994 000099980-000099940-CE9998-N-CE9998 000099980-000099940-EE9994-N-EE9994 000099980-000099940-ER9998-N-ER9998 000099980-000099940-OR9998-N-OR9998 000099980-000099940-PRUEB1-N-PRUEB1 000099980-000099940-PRUMJ1-N-PRUMJ1 000099980-000099940-TE9994-N-TE9994 000099980-000099940-VR9994-N-VR9994 ``` --- # 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-ims-en/utilidades-ims/borrado-tampon-emisor-receptor/informe-preliminar-de-la-bd-de-emision-recepcion.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.