BIG Pega COE Team
Business Rules to be added in EPICs
Category: CA Train
This report presents the exact business rules dynamically extracted from the legacy system. Rules are formatted in an Agile/BDD Given/When/Then structure, offering a bridge between business requirements and technical implementation constraints. Component rules have been logically grouped into feature sets.
🎯 CA Train Scope Detected: Extracted 21 rules, Optimally Merged into 7 Feature Scenarios.
📁 File: GCCIH.cbl
Select All in File
R-GCCIH-cbl-00001 (+6) File: GCCIH.cbl Business Rule: Overview Rules
Rule Belongs to : GCCIH.cbl
Business Justification: Dictates the expected operational logic and validation steps when message processing operation is initiated.
Trigger Criteria:
- Context: A message processing operation is initiated
- Applied to: Initialize Program Control
- Action: The system begins message processing
Logic Flow:
IF A message processing operation is initiated
AND The system begins message processing
THEN:
- • The current program name is saved and the module name becomes the active program identifier
Rule Belongs to : GCCIH.cbl
Business Justification: Dictates the expected operational logic and validation steps when new ih notification needs to be processed.
Trigger Criteria:
- Context: A new IH notification needs to be processed
- Applied to: Prepare IH Notification Data
- Action: The notification data structure is being prepared
Logic Flow:
IF A new IH notification needs to be processed
AND The notification data structure is being prepared
THEN:
- • The input structure is initialized and security byte is set to high values for maximum security
Rule Belongs to : GCCIH.cbl
Business Justification: Defines the strict business conditions required to proceed when ih notification data is prepared with security controls.
Trigger Criteria:
- Context: IH notification data is prepared with security controls
- Applied to: Format CCN Status Message
- Action: The CCN status message is being formatted
Logic Flow:
IF IH notification data is prepared with security controls
AND The CCN status message is being formatted
THEN:
- • The 91-byte input data is moved to positions 2-91 of the message structure and the formatted input is copied to the message area
Rule Belongs to : GCCIH.cbl
Business Justification: Dictates the expected operational logic and validation steps when ccn status message is formatted and ready for processing.
Trigger Criteria:
- Context: A CCN status message is formatted and ready for processing
- Applied to: Format CCN Status Message
- Action: The message is prepared for transmission
Logic Flow:
IF A CCN status message is formatted and ready for processing
AND The message is prepared for transmission
THEN:
- • The accept status is set to spaces to indicate a cleared/ready state
Rule Belongs to : GCCIH.cbl
Business Justification: Establishes the required business protocol to be followed when formatted ccn status message with cleared accept status.
Trigger Criteria:
- Context: A formatted CCN status message with cleared accept status
- Applied to: Send Initial IMS Message
- Action: The message is sent for initial processing
Logic Flow:
IF A formatted CCN status message with cleared accept status
AND The message is sent for initial processing
THEN:
- • The CIMS service is invoked with change operation parameters to process the message
Rule Belongs to : GCCIH.cbl
Business Justification: Governs the functional prerequisites and system routing when message has been processed through initial ims processing.
Trigger Criteria:
- Context: A message has been processed through initial IMS processing
- Applied to: Write Message Log
- Action: The message logging is performed
Logic Flow:
IF A message has been processed through initial IMS processing
AND The message logging is performed
THEN:
- • The WRITMSGL service is invoked with message code, content, length, and module name for complete audit logging
Rule Belongs to : GCCIH.cbl
Business Justification: Establishes the required business protocol to be followed when message has been processed and logged successfully.
Trigger Criteria:
- Context: A message has been processed and logged successfully
- Applied to: Purge IMS Message
- Action: The cleanup operation is performed
Logic Flow:
IF A message has been processed and logged successfully
AND The cleanup operation is performed
THEN:
- • The CIMS service is invoked with purge operation to remove the processed message from the system
R-GCCIH-cbl-00008 (+1) File: GCCIH.cbl Business Rule: Initialize Program Control
Rule Belongs to : GCCIH.cbl
Business Justification: Governs the functional prerequisites and system routing when program control initialization process is starting.
Trigger Criteria:
- Context: A program control initialization process is starting
- Applied to: Save Current Program Name - CC-PROG → PROG-NAME-SAVED
- Action: The system needs to track the current program context
Logic Flow:
IF A program control initialization process is starting
AND The system needs to track the current program context
THEN:
- • The current program identifier must be saved to preserve execution context
Rule Belongs to : GCCIH.cbl
Business Justification: Dictates the expected operational logic and validation steps when current program context has been preserved.
Trigger Criteria:
- Context: The current program context has been preserved
- Applied to: Set Module Name for Tracking - MODULE-NAME → CC-PROG
- Action: The system switches to module execution mode
Logic Flow:
IF The current program context has been preserved
AND The system switches to module execution mode
THEN:
- • The module name must be assigned as the current program identifier for tracking purposes
R-GCCIH-cbl-00010 (+2) File: GCCIH.cbl Business Rule: Prepare IH Notification Data
Rule Belongs to : GCCIH.cbl
Business Justification: Ensures correct system behavior and process compliance when ccn status notification needs to be processed.
Trigger Criteria:
- Context: A CCN status notification needs to be processed
- Applied to: Clear Input Structure
- Action: The system begins preparing the IH notification data
Logic Flow:
IF A CCN status notification needs to be processed
AND The system begins preparing the IH notification data
THEN:
- • The GCX153-INPUT structure is initialized to clear any previous data
Rule Belongs to : GCCIH.cbl
Business Justification: Establishes the required business protocol to be followed when input structure has been initialized for ccn status notification.
Trigger Criteria:
- Context: The input structure has been initialized for CCN status notification
- Applied to: Set Security Parameters to High Values
- Action: Security parameters need to be established
Logic Flow:
IF The input structure has been initialized for CCN status notification
AND Security parameters need to be established
THEN:
- • The GCX153-SECURITY-BYTE is set to HIGH-VALUES to enforce maximum security level
Rule Belongs to : GCCIH.cbl
Business Justification: Defines the strict business conditions required to proceed when input structure is initialized and security parameters are set.
Trigger Criteria:
- Context: The input structure is initialized and security parameters are set
- Applied to: Input Structure Ready for CCN Status
- Action: CCN status data needs to be loaded into the notification structure
Logic Flow:
IF The input structure is initialized and security parameters are set
AND CCN status data needs to be loaded into the notification structure
THEN:
- • 91 bytes of GCWIH data are moved to positions 2-91 of GCX153-INPUT structure
R-GCCIH-cbl-00013 (+3) File: GCCIH.cbl Business Rule: Format CCN Status Message
Rule Belongs to : GCCIH.cbl
Business Justification: Ensures correct system behavior and process compliance when gcwih input structure contains ccn data in positions 1 through 91.
Trigger Criteria:
- Context: GCWIH input structure contains CCN data in positions 1 through 91
- Applied to: Extract CCN Data from GCWIH
- Action: CCN data extraction is initiated
Logic Flow:
IF GCWIH input structure contains CCN data in positions 1 through 91
AND CCN data extraction is initiated
THEN:
- • 91 bytes of CCN data are extracted from GCWIH starting at position 1
Rule Belongs to : GCCIH.cbl
Business Justification: Establishes the required business protocol to be followed when 91 bytes of ccn data have been extracted from gcwih.
Trigger Criteria:
- Context: 91 bytes of CCN data have been extracted from GCWIH
- Applied to: Move CCN Data to Input Structure Position 2-92
- Action: CCN data is moved to the input structure
Logic Flow:
IF 91 bytes of CCN data have been extracted from GCWIH
AND CCN data is moved to the input structure
THEN:
- • CCN data is placed in positions 2 through 92 of GCX153-INPUT structure
Rule Belongs to : GCCIH.cbl
Business Justification: Governs the functional prerequisites and system routing when ccn status message is being prepared.
Trigger Criteria:
- Context: A CCN status message is being prepared
- Applied to: Move CCN Data to Input Structure Position 2-92
- Action: Security initialization is performed
Logic Flow:
IF A CCN status message is being prepared
AND Security initialization is performed
THEN:
- • The security byte is set to HIGH-VALUES indicating maximum security level
Rule Belongs to : GCCIH.cbl
Business Justification: Governs the functional prerequisites and system routing when gcx153-input structure contains properly formatted ccn data with security byte.
Trigger Criteria:
- Context: GCX153-INPUT structure contains properly formatted CCN data with security byte
- Applied to: Transfer Formatted Input to IH Message Structure
- Action: Message structure transfer is initiated
Logic Flow:
IF GCX153-INPUT structure contains properly formatted CCN data with security byte
AND Message structure transfer is initiated
THEN:
- • The complete formatted input is transferred to GCT1531E-MSG for IH processing
R-GCCIH-cbl-00017 File: GCCIH.cbl Business Rule: Send Initial IMS Message
Rule Belongs to : GCCIH.cbl
Business Justification: Ensures correct system behavior and process compliance when message input data has been prepared in gcx153-input structure and accept status is cleared. ⚠️ COBOL Technical Logic
Trigger Criteria:
- Context: Message input data has been prepared in GCX153-INPUT structure and accept status is cleared
- Applied to: Execute CIMS Call with CHNG Function
- Action: System calls CIMS program with CHNG function using CCCOM, ALT-PCB, and GCT1531E parameters
Logic Flow:
IF Message input data has been prepared in GCX153-INPUT structure and accept status is cleared
AND System calls CIMS program with CHNG function using CCCOM, ALT-PCB, and GCT1531E parameters
THEN:
- • IMS message processing is initiated for the prepared message
R-GCCIH-cbl-00018 (+1) File: GCCIH.cbl Business Rule: Write Message Log
Rule Belongs to : GCCIH.cbl
Business Justification: Defines the strict business conditions required to proceed when ccn status notification message needs to be logged.
Trigger Criteria:
- Context: A CCN status notification message needs to be logged
- Applied to: Prepare Log Parameters
- Action: The system prepares logging parameters
Logic Flow:
IF A CCN status notification message needs to be logged
AND The system prepares logging parameters
THEN:
- • The message code, message content, message length, and module name are made available for the logging operation
Rule Belongs to : GCCIH.cbl
Business Justification: Defines the strict business conditions required to proceed when all logging parameters are prepared for the ccn status message. ⚠️ COBOL Technical Logic
Trigger Criteria:
- Context: All logging parameters are prepared for the CCN status message
- Applied to: Call WRITMSGL Program
- Action: The system calls the WRITMSGL program with message code, message content, message length, and module name
Logic Flow:
IF All logging parameters are prepared for the CCN status message
AND The system calls the WRITMSGL program with message code, message content, message length, and module name
THEN:
- • The WRITMSGL program is invoked to log the CCN status notification message
R-GCCIH-cbl-00020 (+1) File: GCCIH.cbl Business Rule: Purge IMS Message
Rule Belongs to : GCCIH.cbl
Business Justification: Ensures correct system behavior and process compliance when message processing has been completed and logged.
Trigger Criteria:
- Context: Message processing has been completed and logged
- Applied to: Execute PURG Function
- Action: System initiates message cleanup process
Logic Flow:
IF Message processing has been completed and logged
AND System initiates message cleanup process
THEN:
- • CIMS program is called with PURG function to purge the message
Rule Belongs to : GCCIH.cbl
Business Justification: Ensures correct system behavior and process compliance when message has been processed and purge function has been executed.
Trigger Criteria:
- Context: Message has been processed and purge function has been executed
- Applied to: Complete Message Processing
- Action: All message operations are completed
Logic Flow:
IF Message has been processed and purge function has been executed
AND All message operations are completed
THEN:
- • System returns control to the calling program to complete the process