🔍
GCX105 - Thematically Grouped Rules
A dual-persona matrix designed specifically for Development scoping. Requirements are hierarchically structured by Epic → Module Program → Business Theme.
Unmapped Subprogram
Module Tracker: GCX105
181 Validations & RulesModule Objective: No description provided from architecture analysis.
⚙️ General Logic & Formats
9 logic blocks
R-GCX105-cbl-00024
Move Message Content to Input Structure
Process Rules
📊 Business Logic Narrative
When the process 'Move Message Content to Input Structure' is invoked, and assuming that a message has been retrieved from the queue with a specific length, when the system processes the message content, the desired outcome is that the message content is moved to the input structure using the determined message length.
💻 Technical Criteria
Given
A message has been retrieved from the queue with a specific length
When
The system processes the message content
Then
The message content is moved to the input structure using the determined message length
R-GCX105-cbl-00054
Set Current Load Date
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Current Load Date' is invoked, and assuming that the system has access to the current machine date, when formatting the log root segment, the desired outcome is that the current machine date in yymmdd format is assigned to the loaded date field in the log root segment.
💻 Technical Criteria
Given
The system has access to the current machine date
When
Formatting the log root segment
Then
The current machine date in YYMMDD format is assigned to the loaded date field in the log root segment
R-GCX105-cbl-00055
Set Current Load Century
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Current Load Century' is invoked, and assuming that the system has access to the current machine century, when formatting the log root segment, the desired outcome is that the current machine century is assigned to the loaded date century field in the log root segment.
💻 Technical Criteria
Given
The system has access to the current machine century
When
Formatting the log root segment
Then
The current machine century is assigned to the loaded date century field in the log root segment
R-GCX105-cbl-00086
Set Load Date and Time
Process Rules
📊 Business Logic Narrative
When the process 'Set Load Date and Time' is invoked, and assuming that a log dependent segment is being formatted, when completing the dependent segment formatting, the desired outcome is that the current machine date is moved to load date field and current machine time is moved to load time field.
💻 Technical Criteria
Given
A log dependent segment is being formatted
When
Completing the dependent segment formatting
Then
The current machine date is moved to load date field and current machine time is moved to load time field
R-GCX105-cbl-00145
Move Message to MMR Message Info Structure
Process Rules
📊 Business Logic Narrative
When the process 'Move Message to MMR Message Info Structure' is invoked, and assuming that a message has been extracted from the input for mmr processing, when the message needs to be structured for mmr format, the desired outcome is that the system moves the message content to the mmr message info structure.
💻 Technical Criteria
Given
A message has been extracted from the input for MMR processing
When
The message needs to be structured for MMR format
Then
The system moves the message content to the MMR message info structure
R-GCX105-cbl-00146
Format MMR Message
Process Rules
📊 Business Logic Narrative
When the process 'Format MMR Message' is invoked, and assuming that a message has been placed in the mmr message info structure, when the message needs to be formatted according to mmr standards, the desired outcome is that the system formats the message content into the standardized mmr message format.
💻 Technical Criteria
Given
A message has been placed in the MMR message info structure
When
The message needs to be formatted according to MMR standards
Then
The system formats the message content into the standardized MMR message format
R-GCX105-cbl-00147
Store Formatted Message in Log Segment
Process Rules
📊 Business Logic Narrative
When the process 'Store Formatted Message in Log Segment' is invoked, and assuming that an mmr message has been properly formatted, when the formatted message needs to be persisted, the desired outcome is that the system stores the formatted mmr message in the log detail segment message field.
💻 Technical Criteria
Given
An MMR message has been properly formatted
When
The formatted message needs to be persisted
Then
The system stores the formatted MMR message in the log detail segment message field
R-GCX105-cbl-00136
Increment Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment Counter' is invoked, and assuming that a log dependent segment has been successfully retrieved, when the segment needs to be processed and stored, the desired outcome is that the working storage subscript counter is incremented by 1.
💻 Technical Criteria
Given
A log dependent segment has been successfully retrieved
When
The segment needs to be processed and stored
Then
The working storage subscript counter is incremented by 1
R-GCX105-cbl-00138
Counter < 100?
Validation Rules
📊 Business Logic Narrative
When the process 'Counter < 100?' is invoked, and assuming that log dependent segments are being retrieved for transfer, when the system checks if more segments can be processed, the desired outcome is that if the counter is less than 100, continue retrieving; otherwise stop the retrieval process.
💻 Technical Criteria
Given
Log dependent segments are being retrieved for transfer
When
The system checks if more segments can be processed
Then
If the counter is less than 100, continue retrieving; otherwise stop the retrieval process
🏷️ CCN & Waybill Identification
21 logic blocks
R-GCX105-cbl-00002
3:Determine Processing Type
Decision Rules
📊 Business Logic Narrative
When the process '3:Determine Processing Type' is invoked, and assuming that a valid authorized request is received, when the transfer ccn flag is set to true, the desired outcome is that the system performs transfer log processing.
💻 Technical Criteria
Given
A valid authorized request is received
When
The transfer CCN flag is set to true
Then
The system performs transfer log processing
R-GCX105-cbl-00003
3:Determine Processing Type
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process '3:Determine Processing Type', assuming that a valid authorized request is received and transfer ccn flag is not set, when the delete log flag is set to true, the desired outcome is that the system performs delete log processing.
💻 Technical Criteria
EXCLUDING
A valid authorized request is received and transfer CCN flag is not set
When
The delete log flag is set to true
Then
The system performs delete log processing
R-GCX105-cbl-00004
3:Determine Processing Type
Decision Rules
📊 Business Logic Narrative
When the process '3:Determine Processing Type' is invoked, and assuming that a valid authorized request is received, when neither transfer ccn flag nor delete log flag is set to true, the desired outcome is that the system performs standard log creation processing.
💻 Technical Criteria
Given
A valid authorized request is received
When
Neither transfer CCN flag nor delete log flag is set to true
Then
The system performs standard log creation processing
R-GCX105-cbl-00005
6:Format Log Root Segment
Process Rules
📊 Business Logic Narrative
When the process '6:Format Log Root Segment' is invoked, and assuming that standard log creation or transfer operation is being performed, when the system needs to create a log root segment, the desired outcome is that the system formats the segment with train or us ccn as key, current machine date and century as loaded date, and record type code from input.
💻 Technical Criteria
Given
Standard log creation or transfer operation is being performed
When
The system needs to create a log root segment
Then
The system formats the segment with train or US CCN as key, current machine date and century as loaded date, and record type code from input
R-GCX105-cbl-00019
22:Find Existing Log Root
Action Rules
📊 Business Logic Narrative
When the process '22:Find Existing Log Root' is invoked, and assuming that a transfer or delete operation is being performed, when the system searches for an existing log root using the provided ccn, the desired outcome is that the system determines if the log root exists and sets the appropriate status flag.
💻 Technical Criteria
Given
A transfer or delete operation is being performed
When
The system searches for an existing log root using the provided CCN
Then
The system determines if the log root exists and sets the appropriate status flag
R-GCX105-cbl-00022
5:Delete Log Processing
Process Rules
📊 Business Logic Narrative
When the process '5:Delete Log Processing' is invoked, and assuming that a delete log operation is requested, when the system locates the log root using the provided ccn, the desired outcome is that the system deletes the entire log structure if found.
💻 Technical Criteria
Given
A delete log operation is requested
When
The system locates the log root using the provided CCN
Then
The system deletes the entire log structure if found
R-GCX105-cbl-00028
Check GCX105-TRANSFER-CCN Flag
Decision Rules
📊 Business Logic Narrative
When the process 'Check GCX105-TRANSFER-CCN Flag' is invoked, and assuming that a transaction message has been received and validated, when the system checks the gcx105-transfer-ccn flag in the input message, the desired outcome is that if the transfer flag is set, route the transaction to transfer log processing workflow.
💻 Technical Criteria
Given
A transaction message has been received and validated
When
The system checks the GCX105-TRANSFER-CCN flag in the input message
Then
If the transfer flag is set, route the transaction to transfer log processing workflow
R-GCX105-cbl-00030
Route to Standard Log Update Processing
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Route to Standard Log Update Processing', assuming that a transaction message has been received and validated, when both the gcx105-transfer-ccn flag and gcx105-delete-log flag are not set, the desired outcome is that route the transaction to standard log update processing workflow to create new log entries.
💻 Technical Criteria
EXCLUDING
A transaction message has been received and validated
When
Both the GCX105-TRANSFER-CCN flag and GCX105-DELETE-LOG flag are not set
Then
Route the transaction to standard log update processing workflow to create new log entries
R-GCX105-cbl-00031
Find Old Log Root by Old CCN
Decision Rules
📊 Business Logic Narrative
When the process 'Find Old Log Root by Old CCN' is invoked, and assuming that a transfer request is received with an old ccn, when the system searches for the existing log root using the old ccn, the desired outcome is that the system determines whether the old log root exists and sets the appropriate status flag.
💻 Technical Criteria
Given
A transfer request is received with an old CCN
When
The system searches for the existing log root using the old CCN
Then
The system determines whether the old log root exists and sets the appropriate status flag
R-GCX105-cbl-00037
Create New Log Root with New CCN
Process Rules
📊 Business Logic Narrative
When the process 'Create New Log Root with New CCN' is invoked, and assuming that all dependent segments have been retrieved and stored, when the system creates the new log structure, the desired outcome is that format new log root with current ccn as key, current machine date, and record type code from input.
💻 Technical Criteria
Given
All dependent segments have been retrieved and stored
When
The system creates the new log structure
Then
Format new log root with current CCN as key, current machine date, and record type code from input
R-GCX105-cbl-00038
Insert New Log Root
Action Rules
📊 Business Logic Narrative
When the process 'Insert New Log Root' is invoked, and assuming that a new log root record has been formatted with current ccn, when the system performs the insert operation, the desired outcome is that insert the log root record and if successful, retrieve it to establish database positioning.
💻 Technical Criteria
Given
A new log root record has been formatted with current CCN
When
The system performs the insert operation
Then
Insert the log root record and if successful, retrieve it to establish database positioning
R-GCX105-cbl-00043
Position to Old Log Root
Process Rules
📊 Business Logic Narrative
When the process 'Position to Old Log Root' is invoked, and assuming that all dependent segments have been successfully transferred to new log structure, when the system prepares to delete the old log structure, the desired outcome is that use get hold unique operation to position on the old log root using the old ccn.
💻 Technical Criteria
Given
All dependent segments have been successfully transferred to new log structure
When
The system prepares to delete the old log structure
Then
Use get hold unique operation to position on the old log root using the old CCN
R-GCX105-cbl-00046
Set CCN as Search Key
Process Rules
📊 Business Logic Narrative
When the process 'Set CCN as Search Key' is invoked, and assuming that a delete log request is being processed, when the system prepares to search for existing log entries, the desired outcome is that the train or us ccn from input is set as the search key for log root lookup.
💻 Technical Criteria
Given
A delete log request is being processed
When
The system prepares to search for existing log entries
Then
The Train or US CCN from input is set as the search key for log root lookup
R-GCX105-cbl-00047
Search for Existing Log Root Entry
Action Rules
📊 Business Logic Narrative
When the process 'Search for Existing Log Root Entry' is invoked, and assuming that the ccn search key has been set, when the system searches for the log root entry in the database, the desired outcome is that the system retrieves the log root entry if it exists or determines it is not found.
💻 Technical Criteria
Given
The CCN search key has been set
When
The system searches for the log root entry in the database
Then
The system retrieves the log root entry if it exists or determines it is not found
R-GCX105-cbl-00049
Delete Complete Log Structure
Action Rules
📊 Business Logic Narrative
When the process 'Delete Complete Log Structure' is invoked, and assuming that a log root entry exists for the specified ccn, when the system processes the delete request, the desired outcome is that the complete log structure including root and all detail records is deleted from the database.
💻 Technical Criteria
Given
A log root entry exists for the specified CCN
When
The system processes the delete request
Then
The complete log structure including root and all detail records is deleted from the database
R-GCX105-cbl-00050
No Action Required - Log Not Found
Process Rules
📊 Business Logic Narrative
When the process 'No Action Required - Log Not Found' is invoked, and assuming that no log root entry exists for the specified ccn, when the system processes the delete request, the desired outcome is that no deletion action is performed and processing continues normally.
💻 Technical Criteria
Given
No log root entry exists for the specified CCN
When
The system processes the delete request
Then
No deletion action is performed and processing continues normally
R-GCX105-cbl-00052
Set Train/CCN as Primary Key
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Train/CCN as Primary Key' is invoked, and assuming that an input message contains a train or us ccn number, when formatting the log root segment, the desired outcome is that the train or us ccn number from the input message is assigned as the primary key in the log root segment.
💻 Technical Criteria
Given
An input message contains a train or US CCN number
When
Formatting the log root segment
Then
The train or US CCN number from the input message is assigned as the primary key in the log root segment
R-GCX105-cbl-00053
Set Train/CCN as Key Value
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Train/CCN as Key Value' is invoked, and assuming that an input message contains a train or us ccn number, when formatting the log root segment, the desired outcome is that the train or us ccn number from the input message is assigned as the key value in the log root segment.
💻 Technical Criteria
Given
An input message contains a train or US CCN number
When
Formatting the log root segment
Then
The train or US CCN number from the input message is assigned as the key value in the log root segment
R-GCX105-cbl-00128
Set Search Key to Old CCN
Process Rules
📊 Business Logic Narrative
When the process 'Set Search Key to Old CCN' is invoked, and assuming that a transfer log operation is being performed, when the system needs to find an existing log root entry, the desired outcome is that the search key is set to the old ccn value from the input message.
💻 Technical Criteria
Given
A transfer log operation is being performed
When
The system needs to find an existing log root entry
Then
The search key is set to the old CCN value from the input message
R-GCX105-cbl-00129
Search Log Database for Root Entry
Action Rules
📊 Business Logic Narrative
When the process 'Search Log Database for Root Entry' is invoked, and assuming that the search key has been set to the old ccn, when the system executes the database search operation, the desired outcome is that a database call is made to retrieve the log root segment using the search criteria.
💻 Technical Criteria
Given
The search key has been set to the old CCN
When
The system executes the database search operation
Then
A database call is made to retrieve the log root segment using the search criteria
R-GCX105-cbl-00141
Remove Log Root Segment from Database
Action Rules
📊 Business Logic Narrative
When the process 'Remove Log Root Segment from Database' is invoked, and assuming that a log root segment exists in the database for the old ccn and the transfer operation has been completed, when the system initiates deletion of the old log root segment, the desired outcome is that the log root segment is permanently removed from the gcslgrt database.
💻 Technical Criteria
Given
A log root segment exists in the database for the old CCN and the transfer operation has been completed
When
The system initiates deletion of the old log root segment
Then
The log root segment is permanently removed from the GCSLGRT database
💰 Bond & Financial Auth
15 logic blocks
R-GCX105-cbl-00001
2:Security Validation
Authorization Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process '2:Security Validation', assuming that a user attempts to access the log processing system, when the security byte is not equal to high-values, the desired outcome is that the system denies access and terminates processing without performing any log operations.
💻 Technical Criteria
EXCLUDING
A user attempts to access the log processing system
When
The security byte is not equal to HIGH-VALUES
Then
The system denies access and terminates processing without performing any log operations
R-GCX105-cbl-00007
8:Format Log Dependent Segment
Computation Rules
📊 Business Logic Narrative
When the process '8:Format Log Dependent Segment' is invoked, and assuming that a log detail segment needs to be created, when the system processes the input date and time, the desired outcome is that the system computes a new key by subtracting the combined date-time value from nines complement to ensure chronological ordering.
💻 Technical Criteria
Given
A log detail segment needs to be created
When
The system processes the input date and time
Then
The system computes a new key by subtracting the combined date-time value from nines complement to ensure chronological ordering
R-GCX105-cbl-00017
19:Insert Log Dependent Segment
Action Rules
📊 Business Logic Narrative
When the process '19:Insert Log Dependent Segment' is invoked, and assuming that a log detail segment has been formatted, when the system attempts to insert the segment and encounters a duplicate key, the desired outcome is that the system automatically decrements the key value and retries insertion up to 50 times.
💻 Technical Criteria
Given
A log detail segment has been formatted
When
The system attempts to insert the segment and encounters a duplicate key
Then
The system automatically decrements the key value and retries insertion up to 50 times
R-GCX105-cbl-00025
Security Byte = HIGH-VALUES?
Authorization Rules
📊 Business Logic Narrative
When the process 'Security Byte = HIGH-VALUES?' is invoked, and assuming that a user attempts to access the log processing system with a security byte value, when the system checks if the security byte equals high-values, the desired outcome is that access is granted if security byte is high-values, otherwise access is denied and processing terminates.
💻 Technical Criteria
Given
A user attempts to access the log processing system with a security byte value
When
The system checks if the security byte equals HIGH-VALUES
Then
Access is granted if security byte is HIGH-VALUES, otherwise access is denied and processing terminates
R-GCX105-cbl-00026
Access Authorized - Continue Processing
Process Rules
📊 Business Logic Narrative
When the process 'Access Authorized - Continue Processing' is invoked, and assuming that security validation has passed successfully, when the security byte equals high-values, the desired outcome is that the system continues to execute the main processing logic for log operations.
💻 Technical Criteria
Given
Security validation has passed successfully
When
The security byte equals HIGH-VALUES
Then
The system continues to execute the main processing logic for log operations
R-GCX105-cbl-00027
Access Denied - Exit Program
Authorization Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Access Denied - Exit Program', assuming that a user attempts to access the system with invalid security credentials, when the security byte does not equal high-values, the desired outcome is that the system denies access and terminates the program without performing any log operations.
💻 Technical Criteria
EXCLUDING
A user attempts to access the system with invalid security credentials
When
The security byte does not equal HIGH-VALUES
Then
The system denies access and terminates the program without performing any log operations
R-GCX105-cbl-00033
Initialize Transfer Variables
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Transfer Variables' is invoked, and assuming that an old log root has been found for transfer, when the system begins transfer processing, the desired outcome is that set dependent segment found flag to true, initialize key value to zero, initialize counter to zero, and clear dependent segment storage area.
💻 Technical Criteria
Given
An old log root has been found for transfer
When
The system begins transfer processing
Then
Set dependent segment found flag to true, initialize key value to zero, initialize counter to zero, and clear dependent segment storage area
R-GCX105-cbl-00063
Generate Unique Key from Date/Time
Computation Rules
📊 Business Logic Narrative
When the process 'Generate Unique Key from Date/Time' is invoked, and assuming that date and time information is available, when creating a log dependent segment, the desired outcome is that a unique key is computed as nines complement minus the combined date-time value and assigned to the dependent segment key.
💻 Technical Criteria
Given
Date and time information is available
When
Creating a log dependent segment
Then
A unique key is computed as nines complement minus the combined date-time value and assigned to the dependent segment key
R-GCX105-cbl-00116
Handle Key Conflicts - Retry with Decremented Key
Process Rules
📊 Business Logic Narrative
When the process 'Handle Key Conflicts - Retry with Decremented Key' is invoked, and assuming that a log dependent segment insertion fails due to duplicate key error (status code 'ii'), when the duplicate key conflict is detected, the desired outcome is that the system should perform retry logic up to 50 times with decremented key values.
💻 Technical Criteria
Given
A log dependent segment insertion fails due to duplicate key error (status code 'II')
When
The duplicate key conflict is detected
Then
The system should perform retry logic up to 50 times with decremented key values
R-GCX105-cbl-00117
Decrement Key Value by 1
Computation Rules
📊 Business Logic Narrative
When the process 'Decrement Key Value by 1' is invoked, and assuming that a duplicate key error has occurred during insert operation, when the retry logic is executed, the desired outcome is that the key value should be decremented by 1 and used for the next insert attempt.
💻 Technical Criteria
Given
A duplicate key error has occurred during insert operation
When
The retry logic is executed
Then
The key value should be decremented by 1 and used for the next insert attempt
R-GCX105-cbl-00176
Decrement Key Value by 1
Computation Rules
📊 Business Logic Narrative
When the process 'Decrement Key Value by 1' is invoked, and assuming that a duplicate key error has been detected during log detail insertion, when the system needs to generate a new unique key for retry, the desired outcome is that the key value should be decremented by 1 from the current value.
💻 Technical Criteria
Given
A duplicate key error has been detected during log detail insertion
When
The system needs to generate a new unique key for retry
Then
The key value should be decremented by 1 from the current value
R-GCX105-cbl-00177
Attempt Insert with New Key
Action Rules
📊 Business Logic Narrative
When the process 'Attempt Insert with New Key' is invoked, and assuming that a new unique key has been generated after a duplicate key error, when the system retries the log detail insertion, the desired outcome is that the insert operation should be attempted using the new decremented key value.
💻 Technical Criteria
Given
A new unique key has been generated after a duplicate key error
When
The system retries the log detail insertion
Then
The insert operation should be attempted using the new decremented key value
R-GCX105-cbl-00119
Duplicate Key Detected?
Process Rules
📊 Business Logic Narrative
When the process 'Duplicate Key Detected?' is invoked, and assuming that a log detail record is being inserted into the database, when the insertion fails due to a duplicate key conflict (status code 'ii'), the desired outcome is that the system decrements the key value by 1 and retries the insertion operation.
💻 Technical Criteria
Given
A log detail record is being inserted into the database
When
The insertion fails due to a duplicate key conflict (status code 'II')
Then
The system decrements the key value by 1 and retries the insertion operation
R-GCX105-cbl-00121
Decrement Key Value by 1
Computation Rules
📊 Business Logic Narrative
When the process 'Decrement Key Value by 1' is invoked, and assuming that a duplicate key conflict exists for a log detail record, when the system needs to resolve the key conflict, the desired outcome is that the system computes a new key by subtracting 1 from the current key value and updates the log detail segment key.
💻 Technical Criteria
Given
A duplicate key conflict exists for a log detail record
When
The system needs to resolve the key conflict
Then
The system computes a new key by subtracting 1 from the current key value and updates the log detail segment key
R-GCX105-cbl-00122
Retry Insert Operation
Action Rules
📊 Business Logic Narrative
When the process 'Retry Insert Operation' is invoked, and assuming that a log detail record key has been decremented to resolve a duplicate key conflict, when the system is ready to retry the insertion, the desired outcome is that the system attempts to insert the log detail record using the modified key value.
💻 Technical Criteria
Given
A log detail record key has been decremented to resolve a duplicate key conflict
When
The system is ready to retry the insertion
Then
The system attempts to insert the log detail record using the modified key value
📍 Routing, Border & Port
2 logic blocks
R-GCX105-cbl-00029
Check GCX105-DELETE-LOG Flag
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Check GCX105-DELETE-LOG Flag', assuming that a transaction message has been received and the transfer flag is not set, when the system checks the gcx105-delete-log flag in the input message, the desired outcome is that if the delete flag is set, route the transaction to delete log processing workflow.
💻 Technical Criteria
EXCLUDING
A transaction message has been received and the transfer flag is not set
When
The system checks the GCX105-DELETE-LOG flag in the input message
Then
If the delete flag is set, route the transaction to delete log processing workflow
R-GCX105-cbl-00044
Old Log Root Still Exists?
Validation Rules
📊 Business Logic Narrative
When the process 'Old Log Root Still Exists?' is invoked, and assuming that the system has positioned to the old log root location, when the positioning operation completes, the desired outcome is that if status indicates successful positioning, proceed with deletion, otherwise complete transfer process.
💻 Technical Criteria
Given
The system has positioned to the old log root location
When
The positioning operation completes
Then
If status indicates successful positioning, proceed with deletion, otherwise complete transfer process
🔁 EDI, Status & Database
69 logic blocks
R-GCX105-cbl-00006
7:Insert Log Root Segment
Action Rules
📊 Business Logic Narrative
When the process '7:Insert Log Root Segment' is invoked, and assuming that a log root segment has been formatted, when the system attempts to insert the segment into the database, the desired outcome is that the system stores the segment and retrieves it if insertion is successful.
💻 Technical Criteria
Given
A log root segment has been formatted
When
The system attempts to insert the segment into the database
Then
The system stores the segment and retrieves it if insertion is successful
R-GCX105-cbl-00008
9:Process Manual Release Messages
Process Rules
📊 Business Logic Narrative
When the process '9:Process Manual Release Messages' is invoked, and assuming that a log detail segment is being formatted, when the action code is 'mmr', the desired outcome is that the system formats the message using mmr message structure.
💻 Technical Criteria
Given
A log detail segment is being formatted
When
The action code is 'MMR'
Then
The system formats the message using MMR message structure
R-GCX105-cbl-00009
10:Process Direct Message Entries
Process Rules
📊 Business Logic Narrative
When the process '10:Process Direct Message Entries' is invoked, and assuming that a log detail segment is being formatted, when the action code is 'zzz', the desired outcome is that the system uses the message as-is without additional formatting.
💻 Technical Criteria
Given
A log detail segment is being formatted
When
The action code is 'ZZZ'
Then
The system uses the message as-is without additional formatting
R-GCX105-cbl-00016
18:Lookup Unknown Action Codes
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process '18:Lookup Unknown Action Codes', assuming that a log detail segment is being formatted, when the action code is not one of the predefined codes, the desired outcome is that the system searches the log table for the action code and uses the corresponding message, or generates an error message if not found.
💻 Technical Criteria
EXCLUDING
A log detail segment is being formatted
When
The action code is not one of the predefined codes
Then
The system searches the log table for the action code and uses the corresponding message, or generates an error message if not found
R-GCX105-cbl-00018
21:Spawn Vista GUI Transaction
Action Rules
📊 Business Logic Narrative
When the process '21:Spawn Vista GUI Transaction' is invoked, and assuming that standard log creation has been completed successfully, when the record type code is 'cc' or 'uc' and both log root and detail insertions were successful, the desired outcome is that the system spawns the gct1511e transaction with the formatted log segments.
💻 Technical Criteria
Given
Standard log creation has been completed successfully
When
The record type code is 'CC' or 'UC' and both log root and detail insertions were successful
Then
The system spawns the GCT1511E transaction with the formatted log segments
R-GCX105-cbl-00020
23:Retrieve Log Dependent Segments
Validation Rules
📊 Business Logic Narrative
When the process '23:Retrieve Log Dependent Segments' is invoked, and assuming that a transfer operation is being performed and the old log root exists, when the system retrieves associated detail records, the desired outcome is that the system collects up to 100 detail records associated with the old log root.
💻 Technical Criteria
Given
A transfer operation is being performed and the old log root exists
When
The system retrieves associated detail records
Then
The system collects up to 100 detail records associated with the old log root
R-GCX105-cbl-00021
24:Delete Old Log Entries
Action Rules
📊 Business Logic Narrative
When the process '24:Delete Old Log Entries' is invoked, and assuming that a transfer operation has successfully created new log entries or a delete operation is requested, when the old log root exists in the system, the desired outcome is that the system deletes the old log root and all associated detail records.
💻 Technical Criteria
Given
A transfer operation has successfully created new log entries or a delete operation is requested
When
The old log root exists in the system
Then
The system deletes the old log root and all associated detail records
R-GCX105-cbl-00023
Call Message Queue Reader
Action Rules
📊 Business Logic Narrative
When the process 'Call Message Queue Reader' is invoked, and assuming that a transaction message exists in the message queue, when the system calls the message queue reader, the desired outcome is that the message is retrieved from the queue for processing.
💻 Technical Criteria
Given
A transaction message exists in the message queue
When
The system calls the message queue reader
Then
The message is retrieved from the queue for processing
R-GCX105-cbl-00032
Old Log Root Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Old Log Root Found?' is invoked, and assuming that the system has searched for an old log root record, when the search operation completes, the desired outcome is that if old log root is found, proceed with transfer initialization, otherwise terminate transfer process.
💻 Technical Criteria
Given
The system has searched for an old log root record
When
The search operation completes
Then
If old log root is found, proceed with transfer initialization, otherwise terminate transfer process
R-GCX105-cbl-00034
Retrieve First Dependent Segment
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve First Dependent Segment' is invoked, and assuming that transfer variables are initialized and old log root exists, when the system retrieves dependent segments using get next parent operation, the desired outcome is that if segment is found, increment counter and store segment in memory array, otherwise set dependent segment not found flag.
💻 Technical Criteria
Given
Transfer variables are initialized and old log root exists
When
The system retrieves dependent segments using get next parent operation
Then
If segment is found, increment counter and store segment in memory array, otherwise set dependent segment not found flag
R-GCX105-cbl-00035
More Segments Available?
Decision Rules
📊 Business Logic Narrative
When the process 'More Segments Available?' is invoked, and assuming that a dependent segment retrieval operation has completed, when the system checks the operation status and counter limits, the desired outcome is that if status indicates success and counter is less than 100, continue retrieval, otherwise proceed to new log creation.
💻 Technical Criteria
Given
A dependent segment retrieval operation has completed
When
The system checks the operation status and counter limits
Then
If status indicates success and counter is less than 100, continue retrieval, otherwise proceed to new log creation
R-GCX105-cbl-00036
Store Segment in Memory
Process Rules
📊 Business Logic Narrative
When the process 'Store Segment in Memory' is invoked, and assuming that a dependent segment has been successfully retrieved, when the segment data is available, the desired outcome is that increment the storage counter and move the segment data to the corresponding position in the memory array.
💻 Technical Criteria
Given
A dependent segment has been successfully retrieved
When
The segment data is available
Then
Increment the storage counter and move the segment data to the corresponding position in the memory array
R-GCX105-cbl-00040
Update Segment Key
Computation Rules
📊 Business Logic Narrative
When the process 'Update Segment Key' is invoked, and assuming that a dependent segment is being processed for transfer, when the segment data is moved to working storage, the desired outcome is that extract the dependent key from the segment and move it to the new key field for insertion.
💻 Technical Criteria
Given
A dependent segment is being processed for transfer
When
The segment data is moved to working storage
Then
Extract the dependent key from the segment and move it to the new key field for insertion
R-GCX105-cbl-00041
Insert Segment to New Log
Action Rules
📊 Business Logic Narrative
When the process 'Insert Segment to New Log' is invoked, and assuming that a dependent segment has been prepared with updated key, when the system performs the insert operation, the desired outcome is that insert the dependent segment as a child of the new log root record.
💻 Technical Criteria
Given
A dependent segment has been prepared with updated key
When
The system performs the insert operation
Then
Insert the dependent segment as a child of the new log root record
R-GCX105-cbl-00045
Delete Old Log Root and All Segments
Action Rules
📊 Business Logic Narrative
When the process 'Delete Old Log Root and All Segments' is invoked, and assuming that the old log root has been located and transfer is complete, when the system performs the delete operation, the desired outcome is that delete the old log root record which cascades to remove all associated dependent segments.
💻 Technical Criteria
Given
The old log root has been located and transfer is complete
When
The system performs the delete operation
Then
Delete the old log root record which cascades to remove all associated dependent segments
R-GCX105-cbl-00048
Log Root Entry Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Log Root Entry Found?' is invoked, and assuming that a search for log root entry has been completed, when the system evaluates the search results, the desired outcome is that if log root entry is found, proceed with deletion; otherwise, no action is required.
💻 Technical Criteria
Given
A search for log root entry has been completed
When
The system evaluates the search results
Then
If log root entry is found, proceed with deletion; otherwise, no action is required
R-GCX105-cbl-00056
Set Record Type Code
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Record Type Code' is invoked, and assuming that an input message contains a record type code, when formatting the log root segment, the desired outcome is that the record type code from the input message is assigned to the record type field in the log root segment.
💻 Technical Criteria
Given
An input message contains a record type code
When
Formatting the log root segment
Then
The record type code from the input message is assigned to the record type field in the log root segment
R-GCX105-cbl-00057
Insert root segment into log database with duplicate handling
Process Rules
📊 Business Logic Narrative
When the process 'Insert root segment into log database with duplicate handling' is invoked, and assuming that a formatted log root segment is ready for insertion into the log database, when the system attempts to insert the log root segment, the desired outcome is that if insertion succeeds, the operation completes successfully, but if insertion fails due to duplicate key, the system retrieves the existing segment to maintain data consistency.
💻 Technical Criteria
Given
A formatted log root segment is ready for insertion into the log database
When
The system attempts to insert the log root segment
Then
If insertion succeeds, the operation completes successfully, but if insertion fails due to duplicate key, the system retrieves the existing segment to maintain data consistency
R-GCX105-cbl-00058
Set Accept Status for Insert
Action Rules
📊 Business Logic Narrative
When the process 'Set Accept Status for Insert' is invoked, and assuming that the system is preparing to insert a log root segment, when the insert operation is initiated, the desired outcome is that the accept status must be set to 'ii' to indicate an insert operation.
💻 Technical Criteria
Given
The system is preparing to insert a log root segment
When
The insert operation is initiated
Then
The accept status must be set to 'II' to indicate an insert operation
R-GCX105-cbl-00059
Insert Successful?
Decision Rules
📊 Business Logic Narrative
When the process 'Insert Successful?' is invoked, and assuming that a log root segment insertion has been attempted and resulted in duplicate key status 'ii', when the system detects the duplicate key condition, the desired outcome is that the system must perform a retrieval operation to get the existing segment using the same key.
💻 Technical Criteria
Given
A log root segment insertion has been attempted and resulted in duplicate key status 'II'
When
The system detects the duplicate key condition
Then
The system must perform a retrieval operation to get the existing segment using the same key
R-GCX105-cbl-00060
Record Insert Status
Process Rules
📊 Business Logic Narrative
When the process 'Record Insert Status' is invoked, and assuming that a log root segment insert operation has been completed (either successful insert or duplicate key handling), when the operation finishes, the desired outcome is that the final status code must be recorded in the working storage indicator for the log root operation.
💻 Technical Criteria
Given
A log root segment insert operation has been completed (either successful insert or duplicate key handling)
When
The operation finishes
Then
The final status code must be recorded in the working storage indicator for the log root operation
R-GCX105-cbl-00061
Initialize Dependent Segment
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Dependent Segment' is invoked, and assuming that a log dependent segment needs to be created, when the format log dependent process begins, the desired outcome is that the dependent segment structure is initialized to clear any previous data.
💻 Technical Criteria
Given
A log dependent segment needs to be created
When
The format log dependent process begins
Then
The dependent segment structure is initialized to clear any previous data
R-GCX105-cbl-00062
Set Date and Time Information
Process Rules
📊 Business Logic Narrative
When the process 'Set Date and Time Information' is invoked, and assuming that input contains date and time information, when formatting the log dependent segment, the desired outcome is that the date is moved to the dependent segment date field and time is moved to the dependent segment time field.
💻 Technical Criteria
Given
Input contains date and time information
When
Formatting the log dependent segment
Then
The date is moved to the dependent segment date field and time is moved to the dependent segment time field
R-GCX105-cbl-00064
Set Action Code and User Information
Process Rules
📊 Business Logic Narrative
When the process 'Set Action Code and User Information' is invoked, and assuming that input contains action code, user id, and sending transaction information, when formatting the log dependent segment, the desired outcome is that the action code is moved to dependent segment action code field, acf2 id is moved to user code field, and sending transaction is moved to transaction field.
💻 Technical Criteria
Given
Input contains action code, user ID, and sending transaction information
When
Formatting the log dependent segment
Then
The action code is moved to dependent segment action code field, ACF2 ID is moved to user code field, and sending transaction is moved to transaction field
R-GCX105-cbl-00065
Format Manual Release Message - MMR
Decision Rules
📊 Business Logic Narrative
When the process 'Format Manual Release Message - MMR' is invoked, and assuming that action code is 'mmr', when processing a manual release action, the desired outcome is that the input message is moved to mmr message info structure and then to the dependent segment message field.
💻 Technical Criteria
Given
Action code is 'MMR'
When
Processing a manual release action
Then
The input message is moved to MMR message info structure and then to the dependent segment message field
R-GCX105-cbl-00066
Format Direct Message - ZZZ
Decision Rules
📊 Business Logic Narrative
When the process 'Format Direct Message - ZZZ' is invoked, and assuming that action code is 'zzz', when processing a direct message action, the desired outcome is that the input message is moved directly to the dependent segment message field without additional formatting.
💻 Technical Criteria
Given
Action code is 'ZZZ'
When
Processing a direct message action
Then
The input message is moved directly to the dependent segment message field without additional formatting
R-GCX105-cbl-00076
Format Transfer From - TFF
Decision Rules
📊 Business Logic Narrative
When the process 'Format Transfer From - TFF' is invoked, and assuming that action code is 'tff', when processing a transfer from action, the desired outcome is that the input message is moved to tff message info structure and then to the dependent segment message field.
💻 Technical Criteria
Given
Action code is 'TFF'
When
Processing a transfer from action
Then
The input message is moved to TFF message info structure and then to the dependent segment message field
R-GCX105-cbl-00077
Format Transfer To - TFT
Decision Rules
📊 Business Logic Narrative
When the process 'Format Transfer To - TFT' is invoked, and assuming that action code is 'tft', when processing a transfer to action, the desired outcome is that the input message is moved to tft message info structure and then to the dependent segment message field.
💻 Technical Criteria
Given
Action code is 'TFT'
When
Processing a transfer to action
Then
The input message is moved to TFT message info structure and then to the dependent segment message field
R-GCX105-cbl-00084
Lookup Unknown Action Code in Table
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Lookup Unknown Action Code in Table', assuming that action code does not match any predefined codes, when processing an unknown action code, the desired outcome is that the system searches the log table for the action code and uses the corresponding message, or generates an error message with the unknown action code if not found.
💻 Technical Criteria
EXCLUDING
Action code does not match any predefined codes
When
Processing an unknown action code
Then
The system searches the log table for the action code and uses the corresponding message, or generates an error message with the unknown action code if not found
R-GCX105-cbl-00143
Receive MMR Action Code
Decision Rules
📊 Business Logic Narrative
When the process 'Receive MMR Action Code' is invoked, and assuming that a log entry is being processed, when the action code equals 'mmr', the desired outcome is that the system identifies this as an mmr message type requiring special formatting.
💻 Technical Criteria
Given
A log entry is being processed
When
The action code equals 'MMR'
Then
The system identifies this as an MMR message type requiring special formatting
R-GCX105-cbl-00144
Extract Message from Input
Process Rules
📊 Business Logic Narrative
When the process 'Extract Message from Input' is invoked, and assuming that an mmr action code has been identified, when the message content needs to be processed, the desired outcome is that the system extracts the message from the gcx105 input structure.
💻 Technical Criteria
Given
An MMR action code has been identified
When
The message content needs to be processed
Then
The system extracts the message from the GCX105 input structure
R-GCX105-cbl-00148
Check Action Code = 'ZZZ'
Decision Rules
📊 Business Logic Narrative
When the process 'Check Action Code = 'ZZZ'' is invoked, and assuming that a log entry is being processed with action code 'zzz', when the system formats the log detail message, the desired outcome is that the input message should be moved directly to the log message field without any formatting or transformation applied.
💻 Technical Criteria
Given
A log entry is being processed with action code 'ZZZ'
When
The system formats the log detail message
Then
The input message should be moved directly to the log message field without any formatting or transformation applied
R-GCX105-cbl-00149
Move Input Message Directly to Log Message
Process Rules
📊 Business Logic Narrative
When the process 'Move Input Message Directly to Log Message' is invoked, and assuming that the action code has been identified as 'zzz', when the message content needs to be stored in the log detail, the desired outcome is that the original input message should be copied directly to the log detail message field without modification.
💻 Technical Criteria
Given
The action code has been identified as 'ZZZ'
When
The message content needs to be stored in the log detail
Then
The original input message should be copied directly to the log detail message field without modification
R-GCX105-cbl-00155
CPZ - Merlin ID Printing
Decision Rules
📊 Business Logic Narrative
When the process 'CPZ - Merlin ID Printing' is invoked, and assuming that a log detail record is being processed, when the action code is 'cpz', the desired outcome is that the system extracts message information into cpz format and moves the formatted cpz message to the log detail message field.
💻 Technical Criteria
Given
A log detail record is being processed
When
The action code is 'CPZ'
Then
The system extracts message information into CPZ format and moves the formatted CPZ message to the log detail message field
R-GCX105-cbl-00161
Format TFT Transfer To Message
Process Rules
📊 Business Logic Narrative
When the process 'Format TFT Transfer To Message' is invoked, and assuming that a log detail record is being processed and the action code is 'tft', when the system processes the message formatting for the log entry, the desired outcome is that the input message is moved to tft message format structure and the formatted tft message is stored in the log detail message field.
💻 Technical Criteria
Given
A log detail record is being processed and the action code is 'TFT'
When
The system processes the message formatting for the log entry
Then
The input message is moved to TFT message format structure and the formatted TFT message is stored in the log detail message field
R-GCX105-cbl-00162
Format TFF Transfer From Message
Process Rules
📊 Business Logic Narrative
When the process 'Format TFF Transfer From Message' is invoked, and assuming that a log detail record is being processed and the action code is 'tff', when the system processes the message formatting for the log entry, the desired outcome is that the input message is moved to tff message format structure and the formatted tff message is stored in the log detail message field.
💻 Technical Criteria
Given
A log detail record is being processed and the action code is 'TFF'
When
The system processes the message formatting for the log entry
Then
The input message is moved to TFF message format structure and the formatted TFF message is stored in the log detail message field
R-GCX105-cbl-00170
Search Log Table for Action Code
Decision Rules
📊 Business Logic Narrative
When the process 'Search Log Table for Action Code' is invoked, and assuming that an action code needs to be processed and a log table with action code entries exists, when the system searches the log table for the matching action code, the desired outcome is that the system either finds the action code entry or reaches the end of the table without finding a match.
💻 Technical Criteria
Given
An action code needs to be processed and a log table with action code entries exists
When
The system searches the log table for the matching action code
Then
The system either finds the action code entry or reaches the end of the table without finding a match
R-GCX105-cbl-00171
Create Error Message with Unknown Action Code
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Create Error Message with Unknown Action Code', assuming that an action code has been searched in the log table, when the action code is not found in any table entry, the desired outcome is that the system creates an error message containing the unknown action code.
💻 Technical Criteria
EXCLUDING
An action code has been searched in the log table
When
The action code is not found in any table entry
Then
The system creates an error message containing the unknown action code
R-GCX105-cbl-00172
Retrieve Message from Table Entry
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Message from Table Entry' is invoked, and assuming that an action code has been searched in the log table, when the action code matches an entry in the table, the desired outcome is that the system retrieves the corresponding message text from that table entry.
💻 Technical Criteria
Given
An action code has been searched in the log table
When
The action code matches an entry in the table
Then
The system retrieves the corresponding message text from that table entry
R-GCX105-cbl-00174
Set Search Index to First Entry
Process Rules
📊 Business Logic Narrative
When the process 'Set Search Index to First Entry' is invoked, and assuming that an action code lookup process needs to be performed, when the system begins the lookup process, the desired outcome is that the system sets the log table index to position 1 to start searching from the first entry.
💻 Technical Criteria
Given
An action code lookup process needs to be performed
When
The system begins the lookup process
Then
The system sets the log table index to position 1 to start searching from the first entry
R-GCX105-cbl-00178
Search Log Table for Matching Action Code
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Search Log Table for Matching Action Code', assuming that an action code that is not handled by the predefined message formatting cases, when the system searches the log table for the action code, the desired outcome is that the system uses the corresponding message from the table if found.
💻 Technical Criteria
EXCLUDING
An action code that is not handled by the predefined message formatting cases
When
The system searches the log table for the action code
Then
The system uses the corresponding message from the table if found
R-GCX105-cbl-00179
Generate Error Message with Unknown Action Code
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Error Message with Unknown Action Code', assuming that an action code that does not exist in the log table, when the table search completes without finding a match, the desired outcome is that the system creates an error message containing the unknown action code.
💻 Technical Criteria
EXCLUDING
An action code that does not exist in the log table
When
The table search completes without finding a match
Then
The system creates an error message containing the unknown action code
R-GCX105-cbl-00181
Set Search Index to 1
Process Rules
📊 Business Logic Narrative
When the process 'Set Search Index to 1' is invoked, and assuming that a need to search the log table for an action code, when the lookup process begins, the desired outcome is that the search index is set to position 1.
💻 Technical Criteria
Given
A need to search the log table for an action code
When
The lookup process begins
Then
The search index is set to position 1
R-GCX105-cbl-00087
Check Action Code = 'MMR'
Decision Rules
📊 Business Logic Narrative
When the process 'Check Action Code = 'MMR'' is invoked, and assuming that a log entry is being processed with an action code, when the action code equals 'mmr', the desired outcome is that the system should extract the message information and format it as a manual release message structure.
💻 Technical Criteria
Given
A log entry is being processed with an action code
When
The action code equals 'MMR'
Then
The system should extract the message information and format it as a manual release message structure
R-GCX105-cbl-00088
Format MMR Message
Process Rules
📊 Business Logic Narrative
When the process 'Format MMR Message' is invoked, and assuming that an action code has been identified as 'mmr', when the message needs to be formatted, the desired outcome is that the system should move the input message to mmr-message-info structure and then move the formatted mmr-message to the log detail message field.
💻 Technical Criteria
Given
An action code has been identified as 'MMR'
When
The message needs to be formatted
Then
The system should move the input message to MMR-MESSAGE-INFO structure and then move the formatted MMR-MESSAGE to the log detail message field
R-GCX105-cbl-00089
Move Input Message Directly to Log Message
Decision Rules
📊 Business Logic Narrative
When the process 'Move Input Message Directly to Log Message' is invoked, and assuming that a log detail record is being formatted for insertion, when the action code from the input message equals 'zzz', the desired outcome is that the input message is moved directly to the log detail message field without any formatting applied.
💻 Technical Criteria
Given
A log detail record is being formatted for insertion
When
The action code from the input message equals 'ZZZ'
Then
The input message is moved directly to the log detail message field without any formatting applied
R-GCX105-cbl-00097
Extract Transfer To Message Info
Decision Rules
📊 Business Logic Narrative
When the process 'Extract Transfer To Message Info' is invoked, and assuming that a log detail record is being processed for message formatting, when the action code is 'tft' indicating a transfer-to operation, the desired outcome is that the system extracts the message information as tft message format and assigns it to the log detail message field.
💻 Technical Criteria
Given
A log detail record is being processed for message formatting
When
The action code is 'TFT' indicating a transfer-to operation
Then
The system extracts the message information as TFT message format and assigns it to the log detail message field
R-GCX105-cbl-00098
Extract Transfer From Message Info
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Extract Transfer From Message Info', assuming that a log detail record is being processed for message formatting and the action code is not 'tft', when the action code is 'tff' indicating a transfer-from operation, the desired outcome is that the system extracts the message information as tff message format and assigns it to the log detail message field.
💻 Technical Criteria
EXCLUDING
A log detail record is being processed for message formatting and the action code is not 'TFT'
When
The action code is 'TFF' indicating a transfer-from operation
Then
The system extracts the message information as TFF message format and assigns it to the log detail message field
R-GCX105-cbl-00111
Search Log Table for Action Code
Decision Rules
📊 Business Logic Narrative
When the process 'Search Log Table for Action Code' is invoked, and assuming that an action code that needs message lookup and a log table with predefined action codes and messages, when the system searches the log table for the action code, the desired outcome is that if the action code is found in the table, the corresponding table message is used; if not found, the system continues to error handling.
💻 Technical Criteria
Given
An action code that needs message lookup and a log table with predefined action codes and messages
When
The system searches the log table for the action code
Then
If the action code is found in the table, the corresponding table message is used; if not found, the system continues to error handling
R-GCX105-cbl-00112
Move Action Code to Error Message
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Move Action Code to Error Message', assuming that an action code that was not found in the log table during search, when the table search completes without finding a match, the desired outcome is that the unknown action code is moved to an error message field and the error message is used as the log message.
💻 Technical Criteria
EXCLUDING
An action code that was not found in the log table during search
When
The table search completes without finding a match
Then
The unknown action code is moved to an error message field and the error message is used as the log message
R-GCX105-cbl-00113
Move Table Message to Log Message
Action Rules
📊 Business Logic Narrative
When the process 'Move Table Message to Log Message' is invoked, and assuming that an action code that exists in the log table with a corresponding message, when the table search finds a matching action code entry, the desired outcome is that the predefined message from the table entry is moved to the log message field.
💻 Technical Criteria
Given
An action code that exists in the log table with a corresponding message
When
The table search finds a matching action code entry
Then
The predefined message from the table entry is moved to the log message field
R-GCX105-cbl-00115
Insert Log Dependent Segment
Action Rules
📊 Business Logic Narrative
When the process 'Insert Log Dependent Segment' is invoked, and assuming that a log dependent segment is ready for insertion into the database, when the insert operation is attempted, the desired outcome is that the segment should be successfully inserted into the log database.
💻 Technical Criteria
Given
A log dependent segment is ready for insertion into the database
When
The insert operation is attempted
Then
The segment should be successfully inserted into the log database
R-GCX105-cbl-00118
Maximum Retries Reached
Process Rules
📊 Business Logic Narrative
When the process 'Maximum Retries Reached' is invoked, and assuming that multiple duplicate key conflicts occur during log dependent segment insertion, when the retry operation is performed 50 times, the desired outcome is that the system should stop retrying and complete the operation.
💻 Technical Criteria
Given
Multiple duplicate key conflicts occur during log dependent segment insertion
When
The retry operation is performed 50 times
Then
The system should stop retrying and complete the operation
R-GCX105-cbl-00175
Duplicate Key Error?
Decision Rules
📊 Business Logic Narrative
When the process 'Duplicate Key Error?' is invoked, and assuming that a log detail record is being inserted into the database, when the insert operation returns a duplicate key status code 'ii', the desired outcome is that the system should check for duplicate key error condition.
💻 Technical Criteria
Given
A log detail record is being inserted into the database
When
The insert operation returns a duplicate key status code 'II'
Then
The system should check for duplicate key error condition
R-GCX105-cbl-00120
Retry Count < 50?
Process Rules
📊 Business Logic Narrative
When the process 'Retry Count < 50?' is invoked, and assuming that a duplicate key conflict occurs during log detail insertion, when the system has already attempted to resolve the conflict multiple times, the desired outcome is that the system performs up to 50 retry attempts before stopping the resolution process.
💻 Technical Criteria
Given
A duplicate key conflict occurs during log detail insertion
When
The system has already attempted to resolve the conflict multiple times
Then
The system performs up to 50 retry attempts before stopping the resolution process
R-GCX105-cbl-00124
Prepare Log Message for Vista
Process Rules
📊 Business Logic Narrative
When the process 'Prepare Log Message for Vista' is invoked, and assuming that log root segment and log dependent segment have been successfully created and are available in memory, when vista gui transaction processing is initiated, the desired outcome is that the system should move the log root segment to vista gui log root segment field and move the log dependent segment to vista gui log dependent segment field.
💻 Technical Criteria
Given
Log root segment and log dependent segment have been successfully created and are available in memory
When
Vista GUI transaction processing is initiated
Then
The system should move the log root segment to Vista GUI log root segment field and move the log dependent segment to Vista GUI log dependent segment field
R-GCX105-cbl-00125
Initialize Vista Transaction
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Vista Transaction' is invoked, and assuming that vista gui message data has been prepared with log segments, when vista transaction initialization is requested, the desired outcome is that the system should move the vista input message to the vista transaction message structure and clear the communication status to prepare for message transmission.
💻 Technical Criteria
Given
Vista GUI message data has been prepared with log segments
When
Vista transaction initialization is requested
Then
The system should move the Vista input message to the Vista transaction message structure and clear the communication status to prepare for message transmission
R-GCX105-cbl-00126
Send Log Message to Vista GUI
Action Rules
📊 Business Logic Narrative
When the process 'Send Log Message to Vista GUI' is invoked, and assuming that vista transaction has been initialized with prepared message data, when message transmission to vista gui is requested, the desired outcome is that the system should change the alternate pcb to prepare for message transmission and write the message to vista gui using the message code, message content, message length, and module name.
💻 Technical Criteria
Given
Vista transaction has been initialized with prepared message data
When
Message transmission to Vista GUI is requested
Then
The system should change the alternate PCB to prepare for message transmission and write the message to Vista GUI using the message code, message content, message length, and module name
R-GCX105-cbl-00127
Complete Vista Transaction
Process Rules
📊 Business Logic Narrative
When the process 'Complete Vista Transaction' is invoked, and assuming that log message has been successfully transmitted to vista gui system, when vista transaction completion is requested, the desired outcome is that the system should purge the alternate pcb to complete the message transmission and finalize the vista gui transaction.
💻 Technical Criteria
Given
Log message has been successfully transmitted to Vista GUI system
When
Vista transaction completion is requested
Then
The system should purge the alternate PCB to complete the message transmission and finalize the Vista GUI transaction
R-GCX105-cbl-00130
Root Entry Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Root Entry Found?' is invoked, and assuming that a database search for log root entry has been executed, when the system evaluates the search results, the desired outcome is that if the database status code is blank spaces, the log root is considered found, otherwise it is considered not found.
💻 Technical Criteria
Given
A database search for log root entry has been executed
When
The system evaluates the search results
Then
If the database status code is blank spaces, the log root is considered found, otherwise it is considered not found
R-GCX105-cbl-00131
Set Status: Old Log Root Found
Process Rules
📊 Business Logic Narrative
When the process 'Set Status: Old Log Root Found' is invoked, and assuming that the database search returned a successful result with blank status code, when the system processes the successful search result, the desired outcome is that the old log root found indicator is set to true.
💻 Technical Criteria
Given
The database search returned a successful result with blank status code
When
The system processes the successful search result
Then
The old log root found indicator is set to true
R-GCX105-cbl-00132
Set Status: Old Log Root Not Found
Process Rules
📊 Business Logic Narrative
When the process 'Set Status: Old Log Root Not Found' is invoked, and assuming that the database search returned a non-successful result with non-blank status code, when the system processes the unsuccessful search result, the desired outcome is that the old log root not found indicator is set to true.
💻 Technical Criteria
Given
The database search returned a non-successful result with non-blank status code
When
The system processes the unsuccessful search result
Then
The old log root not found indicator is set to true
R-GCX105-cbl-00133
Initialize Segment Counter to Zero
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Segment Counter to Zero' is invoked, and assuming that a transfer log operation is being performed, when the system begins retrieving dependent segments from the old log, the desired outcome is that the segment counter is set to zero and dependent segment storage area is cleared.
💻 Technical Criteria
Given
A transfer log operation is being performed
When
The system begins retrieving dependent segments from the old log
Then
The segment counter is set to zero and dependent segment storage area is cleared
R-GCX105-cbl-00134
Get Next Log Dependent Segment
Action Rules
📊 Business Logic Narrative
When the process 'Get Next Log Dependent Segment' is invoked, and assuming that an old log root has been found and dependent segments need to be retrieved, when the system requests the next dependent segment in sequence, the desired outcome is that the system performs a get-next-parent operation to retrieve the next log dependent segment.
💻 Technical Criteria
Given
An old log root has been found and dependent segments need to be retrieved
When
The system requests the next dependent segment in sequence
Then
The system performs a get-next-parent operation to retrieve the next log dependent segment
R-GCX105-cbl-00135
Segment Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Segment Found?' is invoked, and assuming that a get-next-parent operation has been performed on log dependent segments, when the system checks the operation status, the desired outcome is that if the status is successful (space), increment counter and store segment; otherwise set not-found flag.
💻 Technical Criteria
Given
A get-next-parent operation has been performed on log dependent segments
When
The system checks the operation status
Then
If the status is successful (space), increment counter and store segment; otherwise set not-found flag
R-GCX105-cbl-00137
Store Segment in Memory Array
Process Rules
📊 Business Logic Narrative
When the process 'Store Segment in Memory Array' is invoked, and assuming that a log dependent segment has been successfully retrieved and counter incremented, when the segment needs to be preserved for transfer operation, the desired outcome is that the entire log dependent segment is moved to the corresponding position in the working storage segment array.
💻 Technical Criteria
Given
A log dependent segment has been successfully retrieved and counter incremented
When
The segment needs to be preserved for transfer operation
Then
The entire log dependent segment is moved to the corresponding position in the working storage segment array
R-GCX105-cbl-00139
End - All Segments Retrieved
Process Rules
📊 Business Logic Narrative
When the process 'End - All Segments Retrieved' is invoked, and assuming that the system is retrieving log dependent segments, when no more dependent segments are found in the database, the desired outcome is that the retrieval process ends and control returns to the calling procedure.
💻 Technical Criteria
Given
The system is retrieving log dependent segments
When
No more dependent segments are found in the database
Then
The retrieval process ends and control returns to the calling procedure
R-GCX105-cbl-00140
End - Maximum Limit Reached
Process Rules
📊 Business Logic Narrative
When the process 'End - Maximum Limit Reached' is invoked, and assuming that the system is retrieving log dependent segments for transfer, when the segment counter reaches 100, the desired outcome is that the retrieval process stops even if more segments exist in the database.
💻 Technical Criteria
Given
The system is retrieving log dependent segments for transfer
When
The segment counter reaches 100
Then
The retrieval process stops even if more segments exist in the database
R-GCX105-cbl-00142
Initialize Status Codes
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Status Codes' is invoked, and assuming that a deletion operation is about to be performed, when the system prepares for the deletion process, the desired outcome is that all status codes and accept status indicators are cleared to initial state.
💻 Technical Criteria
Given
A deletion operation is about to be performed
When
The system prepares for the deletion process
Then
All status codes and accept status indicators are cleared to initial state
🚂 Equipment & Cargo Specs
65 logic blocks
R-GCX105-cbl-00010
11:Process Cargo Train Operations
Process Rules
📊 Business Logic Narrative
When the process '11:Process Cargo Train Operations' is invoked, and assuming that a log detail segment is being formatted, when the action code is 'cat', 'cdt', 'cfr', 'cpr', 'cpz', or 'ctp', the desired outcome is that the system formats the message using the corresponding message structure for that specific cargo or train operation.
💻 Technical Criteria
Given
A log detail segment is being formatted
When
The action code is 'CAT', 'CDT', 'CFR', 'CPR', 'CPZ', or 'CTP'
Then
The system formats the message using the corresponding message structure for that specific cargo or train operation
R-GCX105-cbl-00011
13:Process Cargo Renumbering
Process Rules
📊 Business Logic Narrative
When the process '13:Process Cargo Renumbering' is invoked, and assuming that a log detail segment is being formatted, when the action code is 'rno' or 'rnn', the desired outcome is that the system formats the message using the corresponding renumbering message structure.
💻 Technical Criteria
Given
A log detail segment is being formatted
When
The action code is 'RNO' or 'RNN'
Then
The system formats the message using the corresponding renumbering message structure
R-GCX105-cbl-00012
15:Process Manual Cargo Changes
Process Rules
📊 Business Logic Narrative
When the process '15:Process Manual Cargo Changes' is invoked, and assuming that a log detail segment is being formatted, when the action code is 'mc' or 'md', the desired outcome is that the system formats the message including the reason code and bond type information.
💻 Technical Criteria
Given
A log detail segment is being formatted
When
The action code is 'MC' or 'MD'
Then
The system formats the message including the reason code and bond type information
R-GCX105-cbl-00013
14:Process Cargo Transfer Operations
Process Rules
📊 Business Logic Narrative
When the process '14:Process Cargo Transfer Operations' is invoked, and assuming that a log detail segment is being formatted, when the action code is 'tft' or 'tff', the desired outcome is that the system formats the message using the corresponding transfer message structure.
💻 Technical Criteria
Given
A log detail segment is being formatted
When
The action code is 'TFT' or 'TFF'
Then
The system formats the message using the corresponding transfer message structure
R-GCX105-cbl-00014
16:Process Equipment Hold Operations
Process Rules
📊 Business Logic Narrative
When the process '16:Process Equipment Hold Operations' is invoked, and assuming that a log detail segment is being formatted, when the action code is 'hnf', 'hid', 'rid', 'szi', or 'szr', the desired outcome is that the system formats the message including the equipment id information.
💻 Technical Criteria
Given
A log detail segment is being formatted
When
The action code is 'HNF', 'HID', 'RID', 'SZI', or 'SZR'
Then
The system formats the message including the equipment ID information
R-GCX105-cbl-00015
18:Lookup Unknown Action Codes
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process '18:Lookup Unknown Action Codes', assuming that a log detail segment is being formatted with action code 'ca', when the bond type field is not empty, the desired outcome is that the system formats the message as 'cargo created automatically tp:' concatenated with the bond type.
💻 Technical Criteria
EXCLUDING
A log detail segment is being formatted with action code 'CA'
When
The bond type field is not empty
Then
The system formats the message as 'CARGO CREATED AUTOMATICALLY TP:' concatenated with the bond type
R-GCX105-cbl-00039
Process Each Stored Segment
Process Rules
📊 Business Logic Narrative
When the process 'Process Each Stored Segment' is invoked, and assuming that new log root has been successfully inserted and dependent segments are stored in memory, when the system processes stored segments using a loop from 1 to 100, the desired outcome is that for each non-empty segment, initialize segment structure and move stored data to working segment.
💻 Technical Criteria
Given
New log root has been successfully inserted and dependent segments are stored in memory
When
The system processes stored segments using a loop from 1 to 100
Then
For each non-empty segment, initialize segment structure and move stored data to working segment
R-GCX105-cbl-00042
More Segments to Transfer?
Decision Rules
📊 Business Logic Narrative
When the process 'More Segments to Transfer?' is invoked, and assuming that a dependent segment has been inserted into the new log structure, when the system checks the loop counter and segment availability, the desired outcome is that if counter is less than or equal to 100 and segment is not empty, continue processing, otherwise proceed to cleanup.
💻 Technical Criteria
Given
A dependent segment has been inserted into the new log structure
When
The system checks the loop counter and segment availability
Then
If counter is less than or equal to 100 and segment is not empty, continue processing, otherwise proceed to cleanup
R-GCX105-cbl-00051
Initialize Root Segment Structure
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Root Segment Structure' is invoked, and assuming that a log root segment structure exists in memory, when the format log root process begins, the desired outcome is that the log root segment structure is initialized to empty values and the input message structure is cleared.
💻 Technical Criteria
Given
A log root segment structure exists in memory
When
The format log root process begins
Then
The log root segment structure is initialized to empty values and the input message structure is cleared
R-GCX105-cbl-00067
Format Cargo Added to Train - CAT
Decision Rules
📊 Business Logic Narrative
When the process 'Format Cargo Added to Train - CAT' is invoked, and assuming that action code is 'cat', when processing a cargo added to train action, the desired outcome is that the input message is moved to cat message info structure and then to the dependent segment message field.
💻 Technical Criteria
Given
Action code is 'CAT'
When
Processing a cargo added to train action
Then
The input message is moved to CAT message info structure and then to the dependent segment message field
R-GCX105-cbl-00068
Format Cargo Deleted from Train - CDT
Decision Rules
📊 Business Logic Narrative
When the process 'Format Cargo Deleted from Train - CDT' is invoked, and assuming that action code is 'cdt', when processing a cargo deleted from train action, the desired outcome is that the input message is moved to cdt message info structure and then to the dependent segment message field.
💻 Technical Criteria
Given
Action code is 'CDT'
When
Processing a cargo deleted from train action
Then
The input message is moved to CDT message info structure and then to the dependent segment message field
R-GCX105-cbl-00069
Format Cargo Print Faxing - CFR
Decision Rules
📊 Business Logic Narrative
When the process 'Format Cargo Print Faxing - CFR' is invoked, and assuming that action code is 'cfr', when processing a cargo print faxing action, the desired outcome is that the input message is moved to cfr message info structure and then to the dependent segment message field.
💻 Technical Criteria
Given
Action code is 'CFR'
When
Processing a cargo print faxing action
Then
The input message is moved to CFR message info structure and then to the dependent segment message field
R-GCX105-cbl-00070
Format Cargo Print Merlin ID - CPR
Decision Rules
📊 Business Logic Narrative
When the process 'Format Cargo Print Merlin ID - CPR' is invoked, and assuming that action code is 'cpr', when processing a cargo print merlin id action, the desired outcome is that the input message is moved to cpr message info structure and then to the dependent segment message field.
💻 Technical Criteria
Given
Action code is 'CPR'
When
Processing a cargo print Merlin ID action
Then
The input message is moved to CPR message info structure and then to the dependent segment message field
R-GCX105-cbl-00071
Format Cargo Print Zebra - CPZ
Decision Rules
📊 Business Logic Narrative
When the process 'Format Cargo Print Zebra - CPZ' is invoked, and assuming that action code is 'cpz', when processing a cargo print zebra action, the desired outcome is that the input message is moved to cpz message info structure and then to the dependent segment message field.
💻 Technical Criteria
Given
Action code is 'CPZ'
When
Processing a cargo print Zebra action
Then
The input message is moved to CPZ message info structure and then to the dependent segment message field
R-GCX105-cbl-00072
Format Cargo Transfer Print - CTP
Decision Rules
📊 Business Logic Narrative
When the process 'Format Cargo Transfer Print - CTP' is invoked, and assuming that action code is 'ctp', when processing a cargo transfer print action, the desired outcome is that the input message is moved to ctp message info structure and then to the dependent segment message field.
💻 Technical Criteria
Given
Action code is 'CTP'
When
Processing a cargo transfer print action
Then
The input message is moved to CTP message info structure and then to the dependent segment message field
R-GCX105-cbl-00073
Format Cargo Renumber Old - RNO
Decision Rules
📊 Business Logic Narrative
When the process 'Format Cargo Renumber Old - RNO' is invoked, and assuming that action code is 'rno', when processing a cargo renumber old action, the desired outcome is that the input message is moved to rno message info structure and then to the dependent segment message field.
💻 Technical Criteria
Given
Action code is 'RNO'
When
Processing a cargo renumber old action
Then
The input message is moved to RNO message info structure and then to the dependent segment message field
R-GCX105-cbl-00074
Format Cargo Renumber New - RNN
Decision Rules
📊 Business Logic Narrative
When the process 'Format Cargo Renumber New - RNN' is invoked, and assuming that action code is 'rnn', when processing a cargo renumber new action, the desired outcome is that the input message is moved to rnn message info structure and then to the dependent segment message field.
💻 Technical Criteria
Given
Action code is 'RNN'
When
Processing a cargo renumber new action
Then
The input message is moved to RNN message info structure and then to the dependent segment message field
R-GCX105-cbl-00075
Format Manual Cargo Change - MC
Decision Rules
📊 Business Logic Narrative
When the process 'Format Manual Cargo Change - MC' is invoked, and assuming that action code is 'mc', when processing a manual cargo change action, the desired outcome is that the input message is moved to mc reason code field, bond type is moved to mc bond type field, and the complete mc message is moved to dependent segment message field.
💻 Technical Criteria
Given
Action code is 'MC'
When
Processing a manual cargo change action
Then
The input message is moved to MC reason code field, bond type is moved to MC bond type field, and the complete MC message is moved to dependent segment message field
R-GCX105-cbl-00078
Format Manual Cargo Delete - MD
Decision Rules
📊 Business Logic Narrative
When the process 'Format Manual Cargo Delete - MD' is invoked, and assuming that action code is 'md', when processing a manual cargo delete action, the desired outcome is that the input message is moved to md reason code field, bond type is moved to md bond type field, and the complete md message is moved to dependent segment message field.
💻 Technical Criteria
Given
Action code is 'MD'
When
Processing a manual cargo delete action
Then
The input message is moved to MD reason code field, bond type is moved to MD bond type field, and the complete MD message is moved to dependent segment message field
R-GCX105-cbl-00079
Format Equipment Hold Not Found - HNF
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Format Equipment Hold Not Found - HNF', assuming that action code is 'hnf', when processing an equipment hold not found action, the desired outcome is that the input message is moved to hnf message equipment id field and the complete hnf message is moved to dependent segment message field.
💻 Technical Criteria
EXCLUDING
Action code is 'HNF'
When
Processing an equipment hold not found action
Then
The input message is moved to HNF message equipment ID field and the complete HNF message is moved to dependent segment message field
R-GCX105-cbl-00080
Format Equipment Hold ID - HID
Decision Rules
📊 Business Logic Narrative
When the process 'Format Equipment Hold ID - HID' is invoked, and assuming that action code is 'hid', when processing an equipment hold id action, the desired outcome is that the input message is moved to hid message equipment id field and the complete hid message is moved to dependent segment message field.
💻 Technical Criteria
Given
Action code is 'HID'
When
Processing an equipment hold ID action
Then
The input message is moved to HID message equipment ID field and the complete HID message is moved to dependent segment message field
R-GCX105-cbl-00081
Format Equipment Release ID - RID
Decision Rules
📊 Business Logic Narrative
When the process 'Format Equipment Release ID - RID' is invoked, and assuming that action code is 'rid', when processing an equipment release id action, the desired outcome is that the input message is moved to rid message equipment id field and the complete rid message is moved to dependent segment message field.
💻 Technical Criteria
Given
Action code is 'RID'
When
Processing an equipment release ID action
Then
The input message is moved to RID message equipment ID field and the complete RID message is moved to dependent segment message field
R-GCX105-cbl-00082
Format Equipment Seize ID - SZI
Decision Rules
📊 Business Logic Narrative
When the process 'Format Equipment Seize ID - SZI' is invoked, and assuming that action code is 'szi', when processing an equipment seize id action, the desired outcome is that the input message is moved to szi message equipment id field and the complete szi message is moved to dependent segment message field.
💻 Technical Criteria
Given
Action code is 'SZI'
When
Processing an equipment seize ID action
Then
The input message is moved to SZI message equipment ID field and the complete SZI message is moved to dependent segment message field
R-GCX105-cbl-00083
Format Equipment Seize Release - SZR
Decision Rules
📊 Business Logic Narrative
When the process 'Format Equipment Seize Release - SZR' is invoked, and assuming that action code is 'szr', when processing an equipment seize release action, the desired outcome is that the input message is moved to szr message equipment id field and the complete szr message is moved to dependent segment message field.
💻 Technical Criteria
Given
Action code is 'SZR'
When
Processing an equipment seize release action
Then
The input message is moved to SZR message equipment ID field and the complete SZR message is moved to dependent segment message field
R-GCX105-cbl-00085
Lookup Unknown Action Code in Table
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Lookup Unknown Action Code in Table', assuming that action code is 'ca' and bond type is not spaces, when processing a cargo created automatically action with bond type, the desired outcome is that the message is formatted as 'cargo created automatically tp:' concatenated with the bond type.
💻 Technical Criteria
EXCLUDING
Action code is 'CA' and bond type is not spaces
When
Processing a cargo created automatically action with bond type
Then
The message is formatted as 'CARGO CREATED AUTOMATICALLY TP:' concatenated with the bond type
R-GCX105-cbl-00150
Process CAT - Cargo Added to Train
Process Rules
📊 Business Logic Narrative
When the process 'Process CAT - Cargo Added to Train' is invoked, and assuming that a cargo train operation with action code 'cat' is being processed, when the system encounters action code 'cat' during message formatting, the desired outcome is that the input message is moved to cat message format structure and then formatted into the log message field.
💻 Technical Criteria
Given
A cargo train operation with action code 'CAT' is being processed
When
The system encounters action code 'CAT' during message formatting
Then
The input message is moved to CAT message format structure and then formatted into the log message field
R-GCX105-cbl-00151
Process CDT - Cargo Deleted from Train
Process Rules
📊 Business Logic Narrative
When the process 'Process CDT - Cargo Deleted from Train' is invoked, and assuming that a cargo train operation with action code 'cdt' is being processed, when the system encounters action code 'cdt' during message formatting, the desired outcome is that the input message is moved to cdt message format structure and then formatted into the log message field.
💻 Technical Criteria
Given
A cargo train operation with action code 'CDT' is being processed
When
The system encounters action code 'CDT' during message formatting
Then
The input message is moved to CDT message format structure and then formatted into the log message field
R-GCX105-cbl-00152
Action Code?
Decision Rules
📊 Business Logic Narrative
When the process 'Action Code?' is invoked, and assuming that a cargo train operation is being processed for message formatting, when the system checks the action code value, the desired outcome is that if action code is 'cat' then process as cargo added to train, else if action code is 'cdt' then process as cargo deleted from train.
💻 Technical Criteria
Given
A cargo train operation is being processed for message formatting
When
The system checks the action code value
Then
If action code is 'CAT' then process as cargo added to train, else if action code is 'CDT' then process as cargo deleted from train
R-GCX105-cbl-00153
CFR - Cargo Print Faxing
Decision Rules
📊 Business Logic Narrative
When the process 'CFR - Cargo Print Faxing' is invoked, and assuming that a log detail record is being processed, when the action code is 'cfr', the desired outcome is that the system extracts message information into cfr format and moves the formatted cfr message to the log detail message field.
💻 Technical Criteria
Given
A log detail record is being processed
When
The action code is 'CFR'
Then
The system extracts message information into CFR format and moves the formatted CFR message to the log detail message field
R-GCX105-cbl-00154
CPR - Cargo Print Operations
Decision Rules
📊 Business Logic Narrative
When the process 'CPR - Cargo Print Operations' is invoked, and assuming that a log detail record is being processed, when the action code is 'cpr', the desired outcome is that the system extracts message information into cpr format and moves the formatted cpr message to the log detail message field.
💻 Technical Criteria
Given
A log detail record is being processed
When
The action code is 'CPR'
Then
The system extracts message information into CPR format and moves the formatted CPR message to the log detail message field
R-GCX105-cbl-00156
CTP - Cargo Train Print
Decision Rules
📊 Business Logic Narrative
When the process 'CTP - Cargo Train Print' is invoked, and assuming that a log detail record is being processed, when the action code is 'ctp', the desired outcome is that the system extracts message information into ctp format and moves the formatted ctp message to the log detail message field.
💻 Technical Criteria
Given
A log detail record is being processed
When
The action code is 'CTP'
Then
The system extracts message information into CTP format and moves the formatted CTP message to the log detail message field
R-GCX105-cbl-00157
Process RNO - Renumber Old Cargo
Decision Rules
📊 Business Logic Narrative
When the process 'Process RNO - Renumber Old Cargo' is invoked, and assuming that a cargo renumbering request is received with action code 'rno', when the system processes the renumbering operation, the desired outcome is that the message is formatted using rno message structure and stored in the log detail message field.
💻 Technical Criteria
Given
A cargo renumbering request is received with action code 'RNO'
When
The system processes the renumbering operation
Then
The message is formatted using RNO message structure and stored in the log detail message field
R-GCX105-cbl-00158
Process RNN - Renumber New Cargo
Decision Rules
📊 Business Logic Narrative
When the process 'Process RNN - Renumber New Cargo' is invoked, and assuming that a cargo renumbering request is received with action code 'rnn', when the system processes the renumbering operation, the desired outcome is that the message is formatted using rnn message structure and stored in the log detail message field.
💻 Technical Criteria
Given
A cargo renumbering request is received with action code 'RNN'
When
The system processes the renumbering operation
Then
The message is formatted using RNN message structure and stored in the log detail message field
R-GCX105-cbl-00159
Format RNO Message with Old Cargo Details
Process Rules
📊 Business Logic Narrative
When the process 'Format RNO Message with Old Cargo Details' is invoked, and assuming that the action code is 'rno' and renumbering information exists in the input message, when the system formats the message for logging, the desired outcome is that the input message is moved to rno message info structure and then to the log detail message field.
💻 Technical Criteria
Given
The action code is 'RNO' and renumbering information exists in the input message
When
The system formats the message for logging
Then
The input message is moved to RNO message info structure and then to the log detail message field
R-GCX105-cbl-00160
Format RNN Message with New Cargo Details
Process Rules
📊 Business Logic Narrative
When the process 'Format RNN Message with New Cargo Details' is invoked, and assuming that the action code is 'rnn' and renumbering information exists in the input message, when the system formats the message for logging, the desired outcome is that the input message is moved to rnn message info structure and then to the log detail message field.
💻 Technical Criteria
Given
The action code is 'RNN' and renumbering information exists in the input message
When
The system formats the message for logging
Then
The input message is moved to RNN message info structure and then to the log detail message field
R-GCX105-cbl-00163
Process MC - Manual Cargo Change
Decision Rules
📊 Business Logic Narrative
When the process 'Process MC - Manual Cargo Change' is invoked, and assuming that a log detail record is being formatted and the action code is 'mc', when the system processes the manual cargo change action, the desired outcome is that the system extracts the reason code from the message field and extracts the bond type from the input and formats the mc message with both reason code and bond type and stores the formatted message in the log dependent segment.
💻 Technical Criteria
Given
A log detail record is being formatted AND the action code is 'MC'
When
The system processes the manual cargo change action
Then
The system extracts the reason code from the message field AND extracts the bond type from the input AND formats the MC message with both reason code and bond type AND stores the formatted message in the log dependent segment
R-GCX105-cbl-00164
Process MD - Manual Cargo Deletion
Decision Rules
📊 Business Logic Narrative
When the process 'Process MD - Manual Cargo Deletion' is invoked, and assuming that a log detail record is being formatted and the action code is 'md', when the system processes the manual cargo deletion action, the desired outcome is that the system extracts the reason code from the message field and extracts the bond type from the input and formats the md message with both reason code and bond type and stores the formatted message in the log dependent segment.
💻 Technical Criteria
Given
A log detail record is being formatted AND the action code is 'MD'
When
The system processes the manual cargo deletion action
Then
The system extracts the reason code from the message field AND extracts the bond type from the input AND formats the MD message with both reason code and bond type AND stores the formatted message in the log dependent segment
R-GCX105-cbl-00165
HNF - Equipment Not Found
Decision Rules
📊 Business Logic Narrative
When the process 'HNF - Equipment Not Found' is invoked, and assuming that an equipment hold operation is being processed, when the action code is 'hnf', the desired outcome is that the system extracts the equipment id from the input message and formats it as an equipment not found message for the log dependent segment.
💻 Technical Criteria
Given
An equipment hold operation is being processed
When
The action code is 'HNF'
Then
The system extracts the equipment ID from the input message and formats it as an equipment not found message for the log dependent segment
R-GCX105-cbl-00166
HID - Equipment Hold
Decision Rules
📊 Business Logic Narrative
When the process 'HID - Equipment Hold' is invoked, and assuming that an equipment hold operation is being processed, when the action code is 'hid', the desired outcome is that the system extracts the equipment id from the input message and formats it as an equipment held message for the log dependent segment.
💻 Technical Criteria
Given
An equipment hold operation is being processed
When
The action code is 'HID'
Then
The system extracts the equipment ID from the input message and formats it as an equipment held message for the log dependent segment
R-GCX105-cbl-00167
RID - Equipment Release
Decision Rules
📊 Business Logic Narrative
When the process 'RID - Equipment Release' is invoked, and assuming that an equipment hold operation is being processed, when the action code is 'rid', the desired outcome is that the system extracts the equipment id from the input message and formats it as an equipment released message for the log dependent segment.
💻 Technical Criteria
Given
An equipment hold operation is being processed
When
The action code is 'RID'
Then
The system extracts the equipment ID from the input message and formats it as an equipment released message for the log dependent segment
R-GCX105-cbl-00168
SZI - Equipment Seize
Decision Rules
📊 Business Logic Narrative
When the process 'SZI - Equipment Seize' is invoked, and assuming that an equipment hold operation is being processed, when the action code is 'szi', the desired outcome is that the system extracts the equipment id from the input message and formats it as an equipment seized message for the log dependent segment.
💻 Technical Criteria
Given
An equipment hold operation is being processed
When
The action code is 'SZI'
Then
The system extracts the equipment ID from the input message and formats it as an equipment seized message for the log dependent segment
R-GCX105-cbl-00169
SZR - Equipment Seize Release
Decision Rules
📊 Business Logic Narrative
When the process 'SZR - Equipment Seize Release' is invoked, and assuming that an equipment hold operation is being processed, when the action code is 'szr', the desired outcome is that the system extracts the equipment id from the input message and formats it as an equipment seize released message for the log dependent segment.
💻 Technical Criteria
Given
An equipment hold operation is being processed
When
The action code is 'SZR'
Then
The system extracts the equipment ID from the input message and formats it as an equipment seize released message for the log dependent segment
R-GCX105-cbl-00173
Format Special Cargo Auto-Creation Message with Bond Type
Computation Rules
📊 Business Logic Narrative
When the process 'Format Special Cargo Auto-Creation Message with Bond Type' is invoked, and assuming that the action code is 'ca' and bond type field contains data, when the system processes the message formatting, the desired outcome is that the system creates a formatted message 'cargo created automatically tp:' concatenated with the bond type value.
💻 Technical Criteria
Given
The action code is 'CA' and bond type field contains data
When
The system processes the message formatting
Then
The system creates a formatted message 'CARGO CREATED AUTOMATICALLY TP:' concatenated with the bond type value
R-GCX105-cbl-00180
Create Special Cargo Auto-Creation Message with Bond Type
Decision Rules
📊 Business Logic Narrative
When the process 'Create Special Cargo Auto-Creation Message with Bond Type' is invoked, and assuming that an action code of 'ca' and a non-blank bond type value, when the message formatting process executes, the desired outcome is that the system creates a message with text 'cargo created automatically tp:' followed by the bond type.
💻 Technical Criteria
Given
An action code of 'CA' and a non-blank bond type value
When
The message formatting process executes
Then
The system creates a message with text 'CARGO CREATED AUTOMATICALLY TP:' followed by the bond type
R-GCX105-cbl-00090
Process Cargo Added to Train - CAT
Decision Rules
📊 Business Logic Narrative
When the process 'Process Cargo Added to Train - CAT' is invoked, and assuming that an input message contains cargo train operation data with action code 'cat', when the system processes the cargo added to train operation, the desired outcome is that the system extracts cargo information from the input message, formats it as a cat message, and stores the formatted message for the log entry.
💻 Technical Criteria
Given
An input message contains cargo train operation data with action code 'CAT'
When
The system processes the cargo added to train operation
Then
The system extracts cargo information from the input message, formats it as a CAT message, and stores the formatted message for the log entry
R-GCX105-cbl-00091
Process Cargo Deleted from Train - CDT
Decision Rules
📊 Business Logic Narrative
When the process 'Process Cargo Deleted from Train - CDT' is invoked, and assuming that an input message contains cargo train operation data with action code 'cdt', when the system processes the cargo deleted from train operation, the desired outcome is that the system extracts cargo information from the input message, formats it as a cdt message, and stores the formatted message for the log entry.
💻 Technical Criteria
Given
An input message contains cargo train operation data with action code 'CDT'
When
The system processes the cargo deleted from train operation
Then
The system extracts cargo information from the input message, formats it as a CDT message, and stores the formatted message for the log entry
R-GCX105-cbl-00092
Extract Cargo Fax Print Information
Decision Rules
📊 Business Logic Narrative
When the process 'Extract Cargo Fax Print Information' is invoked, and assuming that a log detail record is being processed, when the action code is 'cfr' (cargo fax print), the desired outcome is that the system extracts the message as cfr message information and formats it as a cfr message for fax printing.
💻 Technical Criteria
Given
A log detail record is being processed
When
The action code is 'CFR' (Cargo Fax Print)
Then
The system extracts the message as CFR message information and formats it as a CFR message for fax printing
R-GCX105-cbl-00093
Extract Cargo Print Information
Decision Rules
📊 Business Logic Narrative
When the process 'Extract Cargo Print Information' is invoked, and assuming that a log detail record is being processed, when the action code is 'cpr' (cargo print), the desired outcome is that the system extracts the message as cpr message information and formats it as a cpr message for merlin id printing.
💻 Technical Criteria
Given
A log detail record is being processed
When
The action code is 'CPR' (Cargo Print)
Then
The system extracts the message as CPR message information and formats it as a CPR message for Merlin ID printing
R-GCX105-cbl-00094
Process RNO - Renumber From Operation
Decision Rules
📊 Business Logic Narrative
When the process 'Process RNO - Renumber From Operation' is invoked, and assuming that a cargo log entry is being processed, when the action code is 'rno' (renumber from operation), the desired outcome is that the system should extract the original cargo information from the input message and format it as an rno message structure for logging.
💻 Technical Criteria
Given
A cargo log entry is being processed
When
The action code is 'RNO' (Renumber From Operation)
Then
The system should extract the original cargo information from the input message and format it as an RNO message structure for logging
R-GCX105-cbl-00095
Process RNN - Renumber To Operation
Decision Rules
📊 Business Logic Narrative
When the process 'Process RNN - Renumber To Operation' is invoked, and assuming that a cargo log entry is being processed, when the action code is 'rnn' (renumber to operation), the desired outcome is that the system should extract the new cargo information from the input message and format it as an rnn message structure for logging.
💻 Technical Criteria
Given
A cargo log entry is being processed
When
The action code is 'RNN' (Renumber To Operation)
Then
The system should extract the new cargo information from the input message and format it as an RNN message structure for logging
R-GCX105-cbl-00096
Store Formatted Message for Log
Process Rules
📊 Business Logic Narrative
When the process 'Store Formatted Message for Log' is invoked, and assuming that a cargo renumbering message has been formatted (either rno or rnn), when the message formatting is complete, the desired outcome is that the formatted message should be moved to the log detail message field for storage.
💻 Technical Criteria
Given
A cargo renumbering message has been formatted (either RNO or RNN)
When
The message formatting is complete
Then
The formatted message should be moved to the log detail message field for storage
R-GCX105-cbl-00099
Check Action Code
Decision Rules
📊 Business Logic Narrative
When the process 'Check Action Code' is invoked, and assuming that a log detail record is being processed with action code 'mc', when the system processes the manual cargo change action, the desired outcome is that the system extracts the reason code from the input message, extracts the bond type from the input, and formats a manual cargo change message with both pieces of information.
💻 Technical Criteria
Given
A log detail record is being processed with action code 'MC'
When
The system processes the manual cargo change action
Then
The system extracts the reason code from the input message, extracts the bond type from the input, and formats a manual cargo change message with both pieces of information
R-GCX105-cbl-00100
Check Action Code
Decision Rules
📊 Business Logic Narrative
When the process 'Check Action Code' is invoked, and assuming that a log detail record is being processed with action code 'md', when the system processes the manual cargo deletion action, the desired outcome is that the system extracts the reason code from the input message, extracts the bond type from the input, and formats a manual cargo deletion message with both pieces of information.
💻 Technical Criteria
Given
A log detail record is being processed with action code 'MD'
When
The system processes the manual cargo deletion action
Then
The system extracts the reason code from the input message, extracts the bond type from the input, and formats a manual cargo deletion message with both pieces of information
R-GCX105-cbl-00101
HNF - Equipment Not Found
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'HNF - Equipment Not Found', assuming that an input message with action code 'hnf' and equipment information in the message field, when the system processes the equipment not found operation, the desired outcome is that the equipment id is extracted from the input message and formatted into the hnf message structure, which is then stored as the log detail message.
💻 Technical Criteria
EXCLUDING
An input message with action code 'HNF' and equipment information in the message field
When
The system processes the equipment not found operation
Then
The equipment ID is extracted from the input message and formatted into the HNF message structure, which is then stored as the log detail message
R-GCX105-cbl-00102
HID - Equipment Hold
Process Rules
📊 Business Logic Narrative
When the process 'HID - Equipment Hold' is invoked, and assuming that an input message with action code 'hid' and equipment information in the message field, when the system processes the equipment hold operation, the desired outcome is that the equipment id is extracted from the input message and formatted into the hid message structure, which is then stored as the log detail message.
💻 Technical Criteria
Given
An input message with action code 'HID' and equipment information in the message field
When
The system processes the equipment hold operation
Then
The equipment ID is extracted from the input message and formatted into the HID message structure, which is then stored as the log detail message
R-GCX105-cbl-00103
RID - Equipment Release
Process Rules
📊 Business Logic Narrative
When the process 'RID - Equipment Release' is invoked, and assuming that an input message with action code 'rid' and equipment information in the message field, when the system processes the equipment release operation, the desired outcome is that the equipment id is extracted from the input message and formatted into the rid message structure, which is then stored as the log detail message.
💻 Technical Criteria
Given
An input message with action code 'RID' and equipment information in the message field
When
The system processes the equipment release operation
Then
The equipment ID is extracted from the input message and formatted into the RID message structure, which is then stored as the log detail message
R-GCX105-cbl-00104
SZI - Equipment Seize
Process Rules
📊 Business Logic Narrative
When the process 'SZI - Equipment Seize' is invoked, and assuming that an input message with action code 'szi' and equipment information in the message field, when the system processes the equipment seize operation, the desired outcome is that the equipment id is extracted from the input message and formatted into the szi message structure, which is then stored as the log detail message.
💻 Technical Criteria
Given
An input message with action code 'SZI' and equipment information in the message field
When
The system processes the equipment seize operation
Then
The equipment ID is extracted from the input message and formatted into the SZI message structure, which is then stored as the log detail message
R-GCX105-cbl-00105
SZR - Equipment Seize Release
Process Rules
📊 Business Logic Narrative
When the process 'SZR - Equipment Seize Release' is invoked, and assuming that an input message with action code 'szr' and equipment information in the message field, when the system processes the equipment seize release operation, the desired outcome is that the equipment id is extracted from the input message and formatted into the szr message structure, which is then stored as the log detail message.
💻 Technical Criteria
Given
An input message with action code 'SZR' and equipment information in the message field
When
The system processes the equipment seize release operation
Then
The equipment ID is extracted from the input message and formatted into the SZR message structure, which is then stored as the log detail message
R-GCX105-cbl-00106
Format Equipment Not Found Message
Process Rules
📊 Business Logic Narrative
When the process 'Format Equipment Not Found Message' is invoked, and assuming that a log entry request is received with action code 'hnf', when the system processes the message formatting for the log detail record, the desired outcome is that the equipment id from the input message is moved to the hnf message format and the formatted hnf message is assigned to the log detail message field.
💻 Technical Criteria
Given
A log entry request is received with action code 'HNF'
When
The system processes the message formatting for the log detail record
Then
The equipment ID from the input message is moved to the HNF message format and the formatted HNF message is assigned to the log detail message field
R-GCX105-cbl-00107
Format Equipment Not Found Message
Process Rules
📊 Business Logic Narrative
When the process 'Format Equipment Not Found Message' is invoked, and assuming that a log entry request is received with action code 'hid', when the system processes the message formatting for the log detail record, the desired outcome is that the equipment id from the input message is moved to the hid message format and the formatted hid message is assigned to the log detail message field.
💻 Technical Criteria
Given
A log entry request is received with action code 'HID'
When
The system processes the message formatting for the log detail record
Then
The equipment ID from the input message is moved to the HID message format and the formatted HID message is assigned to the log detail message field
R-GCX105-cbl-00108
Format Equipment Not Found Message
Process Rules
📊 Business Logic Narrative
When the process 'Format Equipment Not Found Message' is invoked, and assuming that a log entry request is received with action code 'rid', when the system processes the message formatting for the log detail record, the desired outcome is that the equipment id from the input message is moved to the rid message format and the formatted rid message is assigned to the log detail message field.
💻 Technical Criteria
Given
A log entry request is received with action code 'RID'
When
The system processes the message formatting for the log detail record
Then
The equipment ID from the input message is moved to the RID message format and the formatted RID message is assigned to the log detail message field
R-GCX105-cbl-00109
Format Equipment Not Found Message
Process Rules
📊 Business Logic Narrative
When the process 'Format Equipment Not Found Message' is invoked, and assuming that a log entry request is received with action code 'szi', when the system processes the message formatting for the log detail record, the desired outcome is that the equipment id from the input message is moved to the szi message format and the formatted szi message is assigned to the log detail message field.
💻 Technical Criteria
Given
A log entry request is received with action code 'SZI'
When
The system processes the message formatting for the log detail record
Then
The equipment ID from the input message is moved to the SZI message format and the formatted SZI message is assigned to the log detail message field
R-GCX105-cbl-00110
Format Equipment Not Found Message
Process Rules
📊 Business Logic Narrative
When the process 'Format Equipment Not Found Message' is invoked, and assuming that a log entry request is received with action code 'szr', when the system processes the message formatting for the log detail record, the desired outcome is that the equipment id from the input message is moved to the szr message format and the formatted szr message is assigned to the log detail message field.
💻 Technical Criteria
Given
A log entry request is received with action code 'SZR'
When
The system processes the message formatting for the log detail record
Then
The equipment ID from the input message is moved to the SZR message format and the formatted SZR message is assigned to the log detail message field
R-GCX105-cbl-00114
Format Special Cargo Message with Bond Type
Computation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Format Special Cargo Message with Bond Type', assuming that an action code of 'ca' and a bond type field that is not empty, when the system processes the cargo creation action, the desired outcome is that a formatted message is created containing 'cargo created automatically tp:' followed by the bond type value.
💻 Technical Criteria
EXCLUDING
An action code of 'CA' and a bond type field that is not empty
When
The system processes the cargo creation action
Then
A formatted message is created containing 'CARGO CREATED AUTOMATICALLY TP:' followed by the bond type value
R-GCX105-cbl-00123
Start Vista GUI Transaction
Decision Rules
📊 Business Logic Narrative
When the process 'Start Vista GUI Transaction' is invoked, and assuming that a log record has been processed with a specific record type code and processing status indicators, when the record type code is 'cc' (canadian cargo) or 'uc' (us cargo) and both log root insertion and log dependent insertion were successful, the desired outcome is that the system should initiate vista gui transaction processing.
💻 Technical Criteria
Given
A log record has been processed with a specific record type code and processing status indicators
When
The record type code is 'CC' (Canadian Cargo) or 'UC' (US Cargo) and both log root insertion and log dependent insertion were successful
Then
The system should initiate Vista GUI transaction processing