Skip to content

PRICEGEN CLP

The provided CLP (Control Language Program) named PRICEGEN.clp is designed to run a complete pricing generation process for a program or file named PRSABLW. Below, I will explain the process steps of the program, list the external programs called, and identify the tables (files) used.

Process Steps of the CLP Program

  1. Program Declaration and Parameter Input:
  2. The program accepts a single input parameter &P$GRP, a 1-character variable.

  3. Example: If &P$GRP is 'A', it is used to construct other variables and file names.

  4. Variable Declarations:

  5. &PARM9: A 10-character variable initialized as ',,,,,,,,' concatenated with &P$GRP. This creates a parameter string like ',,,,,,,,A' for passing to external programs.
  6. &PRSABLW: An 8-character variable constructed by concatenating &P$GRP with 'PRSABLW'. For example, if &P$GRP is 'A', then &PRSABLW becomes 'APRSABLW'. This represents the name of a file to be used.

  7. &MSGID and &ERRMSG: Variables for error handling, though not used explicitly in the provided code beyond declaration.

  8. Start System/36 Procedure GSY2K:

  9. The program calls STRS36PRC PRC(GSY2K), which initiates a System/36 procedure named GSY2K. This likely performs some initialization or setup for the pricing generation process.

  10. No parameters are passed to GSY2K.

  11. Clear Physical File:

  12. The CLRPFM FILE(&PRSABLW) command clears the contents of the physical file named by &PRSABLW (e.g., APRSABLW if &P$GRP is 'A').

  13. This step prepares the file for new data by removing existing records.

  14. Error Handling for File Clearing:

  15. The program monitors for specific error message IDs (SYS3827, CPF3156, CPF3130, SSP0010) using MONMSG.
  16. If any of these errors occur during the CLRPFM operation, the program jumps to the ERROR label, which immediately ends the program (ENDPGM).

  17. These message IDs typically correspond to issues like file not found, authority errors, or file in use.

  18. Call External System/36 Procedures:

  19. If no errors occur during the file clearing, the program calls a series of System/36 procedures, each passing the &PARM9 parameter (e.g., ',,,,,,,,A'). The procedures are:
    • BIFX43
    • BIFX44
    • BI944B
    • BI942E
    • PRICES

  20. These procedures likely perform specific steps in the pricing generation process, such as data processing, calculations, or updates to the PRSABLW file.

  21. Error Handling and Program Termination:

  22. If any of the monitored errors occur during the CLRPFM step, the program jumps to the ERROR label and terminates with ENDPGM.
  23. If no errors occur, the program executes all procedures and ends normally.

External Programs Called

The CLP program calls the following external System/36 procedures: 1. GSY2K (no parameters) 2. BIFX43 (with parameter &PARM9) 3. BIFX44 (with parameter &PARM9) 4. BI944B (with parameter &PARM9) 5. BI942E (with parameter &PARM9) 6. PRICES (with parameter &PARM9)

Tables (Files) Used

The program explicitly references one file: - &PRSABLW: A physical file whose name is dynamically constructed based on the input parameter &P$GRP (e.g., APRSABLW for &P$GRP = 'A'). This file is cleared using the CLRPFM command and is likely used or updated by the called procedures.

Additional Notes

  • The program is written for an IBM AS/400 (iSeries) environment, using CLP to interact with System/36-compatible procedures (STRS36PRC), indicating a legacy system or compatibility mode.
  • The exact functionality of the called procedures (GSY2K, BIFX43, etc.) is not specified in the code, but they are likely responsible for generating or updating pricing data in the PRSABLW file.
  • The error handling is minimal, only covering the CLRPFM operation. Errors during the STRS36PRC calls are not explicitly monitored, which could lead to silent failures if those procedures encounter issues.
  • The &MSGID and &ERRMSG variables are declared but not used, suggesting potential incomplete error handling or a placeholder for future enhancements.

If you need further analysis, such as the specific roles of the called procedures or additional context about the PRSABLW file, please provide more details or related documentation!