Engineering Data Support

Chapter 3. Batch programs

The batch programs supplied with CEDS are described in this chapter. The sample JCL to run these programs can be found on the TFG2000 Base Product tape.

Note: This chapter documents Diagnosis, Modification, and Tuning Information, which is provided to help the customer do diagnosis, modification, and tuning of CEDS

Warning!
Do not use this Diagnosis, Modification, and Tuning Information as a programming interface.

This chapter describes the following programs:

Program	Description
EMTBBMWI	Initializes BOMWORK database
EMTBBOM	Unloads bill of material in PDI Format
EMTBEXIT	Controls synchronization of accesses to CEDS interface files
FTPSECUR	Ensures a CEDS interface or feedback data set can be allocated by the FTP

The information is presented in the following format:

Purpose

Briefly describes the program's use within CEDS and its relationship with a transaction or with other programs when the program is used as an external subroutine.

Reference data

Provides formal program reference material, such as:

• PSB Name
• Copybooks
• Linked to Programs
• Loaded Programs
• Database Access chart

Database access chart shows the database segments accessed by the program's PSBs and whether the access is for reference only or for updating. This chart lists the following:

• Internal database name
• Internal segment name
• Segment description
• Access mode

Note: For more information on the database access chart, see Appendix A. "How to use the charts", of this manual.

Input control record chart

Shows the details of the input control records that are required for the batch programs. This chart lists the following:

• Parameter position
• Parameter length
• Parameter description
• Parameter value range
• Default value

Note: For more information on the input control record chart, see Appendix A. "How to use the charts", of this manual.

Output produced

Describes the output that results from the running of the program.

Report field/database field cross-reference chart

Describes the relationship between report field names and database field names for a program. This chart lists the following:

• Report field name
• Report field description
• Internal segment field name
• Internal segment name
• Internal database name

Note: For more information on the Report Field/Database Field Cross-Reference Chart, see Appendix A. "How to use the charts", of this manual.

Additional information

Provides additional descriptive comments to help you when reading the program source code. In general, these comments expand the explanation of the main functions supported and, in certain cases, describe processing techniques used.

Outline of program flow

Provides a high-level description of the logic used in the program, including the major procedure names and database calls used.

EMTBBMWI: Initialize BOMWORK database

Purpose

This program initially loads the BOMWORK database to create a control record with default values.

Reference data

PSB Name

EMTPBWE

Loaded Program

ENVTABLE

Database Access

Outline of program flow

Main program flow

• Open printer file.

• Setup CEDS control record.

• Perform DL/I insert.

• If DL/I status is successful, then:

   

  Write BOMWORK initialization successful to printer.

  Else

   

   

  Write BOMWORK initialization unsuccessful to printer.

• Go back.

EMTBBOM: Unload bill of material in PDI format

Purpose

This program reads the Product Definition Database, then creates records for items and bills of material in the PDI format.

Reference data

PSB Name

EMTPBBx (x = environment)

Copybooks

DATEOS	ENGCHGS	ENVTABLE	FIELDOS1
FUNCTINS	ITEMIDS	ITMDATS	ITMTXTS
PCB1	PCB2	PCB3	PCB4
PROCERR	PRODSTS	STDATAS	STDXIDS

Loaded Program

ENVTABLx (x = environment)

Database Access

Database	Segment	Segment Description	Mode
PRDEFDB	ITEMID	Item identification	R/O
PRDEFDB	ITMDAT	Item data	R/O
PRDEFDB	ITMTXT	Item comments	R/O
PRDEFDB	ENGCHG	Engineering change	R/O
PRDEFDB	PRODST	Product structure	R/O
DDXDT0E	STDIX	Text identification	R/O
DDXDT0E	STDATA	Standard text data	R/O

Output produced

The program creates a status report that reveals the success of the run and the number of items processed or unloaded.

Fields passed from TFG2000 to Product Data Interface (PDI)

Outline of program flow

Main Program Flow

1. Perform Initialization-Routine.
2. Perform Create-Admin-Start-Routine.
3. Perform Write-EREC-Routine.
4. Perform Write-ERAI-Routine.
5. Perform Write-Item-Objects-Routine.
6. Perform Write-BOM-Objects-Routine.
7. Perform Write-Promote-Objects-Routine.
8. Perform Report-Processing-Routine.

Initialization-Routine

1. Open PRINT datafile.
   • If unable to open PRINT datafile perform Error-Routine.
2. Open PARAMETER file.
   • If unable to open PARAMETER file, perform Error-Routine.

     Else

      

     Perform Process-Parameter-Record.

3. Load Environment Table.
4. Open PDI datafile.
   • If unable to open PDI datafile perform Error-Routine.
5. Open VSAM workfiles.
   • If unable to open VSAM workfiles perform Error-Routine.
6. Load translate table from Standard Text database.

Process-Parameter-Record

1. Read parameter record.
   • If unable to read parameter record perform Error-Routine.
2. Process parameter information.

Create-Admin-Start-Routine

1. Loop through all Items in Product Definition database.
   • Loop through all ENGCHG segments for this item.
     • Create a VSAM-1 workfile containing EC information with EC number.
2. Create and write the Admin Header, Data Dictionary, and CIP objects.

Write-EREC-Routine.

1. Loop through VSAM-1 file.
   • Create a VSAM-2 workfile containing all ECs with key of effectivity date and EC number.
   • Setup and write the EUOEB600 object.
2. Create and write a dummy EUOEB600 object if none written.

Write-ERAI-Routine

1. Loop through all Items in Product Definition database.
   • Loop through all ENGCHG segments of ITEMID.
     • Build a VSAM-3 file containing all ECs for this Item with key of effectivity date and EC sequence number.
   • Loop through all entries in VSAM-3.
     • Setup and write the EUOEB700 object.
   • Create and write a dummy EC EUOEB700 object if no ECs exist.

Write-Item-Objects-Routine

1. Loop through all Items in Product Definition database.
   • Create and write the EUOSB211 object.
   • Create and write the EUOSB271 object.
   • Create and write the EUOSB291 object.
   • Create and write the EUOSB151 object, if ITMTXT exists.

Write-BOM-Objects-Routine

1. Loop through all Items in Product Definition database.
   • Loop through all ENGCHG segments for this ITEMID.
     • Build a VSAM-3 file containing all ECs for this Item with key of effectivity date and EC sequence number.
   • Loop through all entries in VSAM-3.
     • Scan PRODST of ITEMID for match against this VSAM-3 entry.
     • If match

       Create and write the EUOSB111 object, if none written for this item.

       Create and write the EUOSA121 object.

   • Delete VSAM-3.

Write-Promote-Objects-Routine

1. Create and write the Admin Header and Data Dictionary.
2. Loop through all entries of VSAM-2.
   • Create and write the EUOSA001 object.

Error-Routine

1. Obtain error message.
2. Print message.
3. Close any open files.
4. Stop program processing.

Report-Processing-Routine

1. Print summary information.
2. Close any open files.
3. Stop program processing.

EMTBEXIT: Control access to CEDS interface files

Purpose

This program controls the synchronization of accesses to CEDS interface files (EMTVMKx, EMTVEKx, EMTVDKx, EMTV1KE, and EMTV1EE). The program is called from batch program FTPSECUR upon open or close of a file. It establishes exclusive control over the CEDS interface files by placing a flag in the file EMTVIKE. The flag must be reset before other programs can access the file. In addition to controlling access to the files, the program also cleans up after the transmission of feedback data. The program deletes all records in the feedback files after the feedback data is transmitted.

Outline of program flow

Main program flow

• If file name is not dynamic, then perform 200-PROCESS.

• If receive or open (dynamic PES feedback file or dynamic PDI feedback file):
  • Perform 100-EXTRACT-FILE-NAME.
  • Perform 200-PROCESS.
  • Perform 130-REPLACE-FILE-NAME.

• Else
  • Perform 100-EXTRACT-FILE-NAME.
  • Perform 130-REPLACE-FILE-NAME.

• Go back.

100-EXTRACT-FILE-NAME

• Scan file name for VSAM delimiter.
• Build file name from characters following last VSAM delimiter.

130-REPLACE-FILE-NAME

• IF PES feedback, then use dynamic PES file name.

  Else

   

• If PDI feedback, then use dynamic PDI file name.

200-PROCESS

If CEDS file, then perform 210-PROCESS-ILOCK.

210-PROCESS-ILOCK

• If open, then set in-use flag.

  Else

   

  • Reset in-use flag.
  • If send, then
    • Perform 310-OPEN-FEEDBACK.
    • Perform 320-READ-FEEDBACK.
    • Perform 330-DELETE-FEEDBACK until end-of-file.
    • Perform 340-CLOSE-FEEDBACK.
• perform 400-PROCESS-INTERLOCK

310-OPEN-FEEDBACK

• If static PES feedback file, then open static PES.

  Else

   

• If static PDI feedback file, then:

   

  Open static PDI.

  Else

   

• If dynamic PES feedback file, then:

   

  Open dynamic PES.

  Else

   

   

  If dynamic PDI feedback file, then open dynamic PDI.

• If not successful, then:
  • Perform 400-PROCESS-INTERLOCK.
  • Go back.

320-READ-FEEDBACK

• If static PES feedback file, then:

   

  Read next static PES record.

  Else

   

   

  If static PDI feedback file, then read next static PDI record.

  Else

   

• If dynamic PES feedback file, then:

   

  Read next dynamic PES record.

  Else

   

   

  If dynamic PDI feedback file, then read next dynamic PDI record.

• If not successful and not end-of-file, then:
  • Perform 400-PROCESS-INTERLOCK.
  • Go back.

330-DELETE-FEEDBACK

• If static PES feedback file, then:

   

  DELETE record from static PES feedback file.

  Else

   

   

  If static PDI feedback file, then:

   

  Delete record from static PDI feedback file:

  Else

   

   

  If dynamic PES feedback file, then delete record from dynamic PES feedback file.

  Else

   

   

  If dynamic PDI feedback file, then delete record from dynamic PDI feedback file.

• If not successful, then:
  • Perform 400-PROCESS-INTERLOCK.
  • Go back.
• Perform 320-READ-FEEDBACK.

340-CLOSE-FEEDBACK

 

If static PES feedback file, then close static PES file.

Else

 

 

If static PDI feedback file, then close static PDI file.

Else

 

 

If dynamic PES feedback file, then close dynamic PES file.

Else

 

 

If dynamic PDI feedback file, then close dynamic PDI file.

 

If not successful, then:

• Perform 400-PROCESS-INTERLOCK.
• Go back.

400-PROCESS-INTERLOCK

• Perform 410-OPEN-INTERLOCK.
• Perform 420-READ-WRITE-INTERLOCK.
• Perform 430-CLOSE-INTERLOCK.

410-OPEN-INTERLOCK.

• Open interlock file.
• If not successful, then perform 427-REWRITE-INTERLOCK.

  Else

   

• Go back.

420-READ-WRITE-INTERLOCK

• Read interlock file for file name.
• If not found, then perform 423-WRITE-INTERLOCK.
• If not successful, then:
• Go back.

423-WRITE-INTERLOCK

• Write interlock record.
• If not successful, then:
  • Go back.

• Rewrite interlock record.
• If not successful, then:
  • Go back.

430-CLOSE-INTERLOCK

• Close interlock file.
• If not successful, then:
  • Go back.

FTPSECUR: Allocate interface or feedback data

Purpose

This program is a modified version of the FTPSECUR program provided by FTP. It was modified for CEDS users to ensure that CEDS interface or feedback data set can be allocated by FTP. It sets a flag in an interlock file by calling EMTBEXIT to prevent CEDS from accessing either interface or feedback files. It then attempts to open the file. If the program cannot open the file, the program waits up to 10 minutes for the file to become available. It then returns control to the FTP to send or receive the file. After sending the file, it resets the flag in the interlock file by calling EMTBEXIT to allow CEDS access to the feedback or interface files.

If you have an existing FTPSECUR program, the changes described above must be integrated into the existing FTPSECUR functions.

Note: This program is written in assembler language.

Reference data

Called to Programs

EMTBEXIT

Outline of program flow

Main program flow

• Save the registers in caller's save area.

• Address the FTP parameter list.

• If command is 'open' and sending node:

  • Load parameter list with send file information.

  • Call EMTBEXIT to set interlock flag.

  • If send file is a feedback file:
    • Load ACB address.
    • Set counter to 20.
    • Go to OPEN FILE.

• If command is 'open' and receiving node:
  • Load parameter list with receive file information.
  • Call EMTBEXIT to set interlock flag.
  • Load ACB address.
  • Set counter to 20.
  • Go to OPEN FILE.

• If command is 'close' and sending node:
  • Load parameter list with send file information.
  • Call EMTBEXIT to reset interlock flag.

• If command is 'close' and receiving node.
  • Load parameter list with receive file information.
  • Call EMTBEXIT to reset interlock flag.

Exit

• Restore registers from save area.
• Return to FTP.

OPEN FILE

• Open the file.

• If open is successful:
  • Close the file.
  • Go to EXIT.

• Else
  • Delay 30 seconds.
  • Subtract one from counter.
  • If counter is zero:
    • Go to EXIT.
  • Else
    • Go to OPEN FILE.