Detailed EDI User Stories

As an EDI Gateway Service,
I want to orchestrate and execute all GCCTBIO EDI data mapping and validation logic,
So that I can ensure strict compliance with US Customs (P140) automated payload constraints in a single consolidated service.

Prerequisites & Setup

[8:Initialize Root Segment SSA]
The SSA flag indicates qualified search is required → The system sets the root segment key value for targeted access
[9:Initialize Dependent Segment SSA]
The unqualified SSA flag is not set → The system sets both root segment key value and dependent segment key value for hierarchical access
[9:Initialize Dependent Segment SSA]
The segment name is neither GCSTBRT (root) nor GCSTBDP (dependent) → The system marks the operation as not valid and prevents database access

Core Acceptance Criteria

[10:Handle Dependent Segment Unqualified Access]
Either the unqualified SSA flag is set or the SSA flag indicates unqualified search → The system sets only the root segment key value and configures unqualified SSA for broader search scope
[11:Route Root Segment Access, 14:Route Dependent Segment Access]
The operation is ready for database access → The system routes to primary PCB if second PCB flag is not set, otherwise routes to secondary PCB
[12:Execute Root Segment Database Call with Primary PCB]
The SSA configuration determines the call parameters → The system calls CIMS with appropriate SSA parameters: qualified SSA for targeted access, unqualified SSA for broader access, or no SSA for direct operations
[13:Execute Root Segment Database Call with Secondary PCB]
The SSA configuration determines the call parameters → The system calls CIMS with secondary PCB and appropriate SSA parameters: qualified SSA for targeted access, unqualified SSA for broader access, or no SSA for direct operations
[15:Execute Dependent Segment Database Call with Primary PCB]
The SSA configuration determines the call parameters → The system calls CIMS with hierarchical SSA parameters: both root and dependent qualified SSAs for targeted access, root qualified and dependent unqualified SSAs for mixed access, or no SSA for direct operations
[16:Execute Dependent Segment Database Call with Secondary PCB]
The SSA configuration determines the call parameters → The system calls CIMS with secondary PCB and hierarchical SSA parameters: both root and dependent qualified SSAs for targeted access, root qualified and dependent unqualified SSAs for mixed access, or no SSA for direct operations
[Configure Unqualified SSA for Insert]
The system configures the segment search argument → The SSA flag should be set to unqualified SSA type for insert processing
[Check if Segment is Root Segment]
If the segment name against the root segment identifier → The system determines if the segment is a root segment type and routes accordingly
[SSA Type = QUALIFIED-SSA?]
The system checks the SSA flag type for qualified search requirements → The system determines whether to use qualified or unqualified SSA for the root segment access
[Set Root Segment Key Value]
The SSA flag indicates qualified search is needed → The system assigns the root segment key value to enable precise segment access
[Skip Key Setup]
The SSA flag indicates unqualified search is acceptable → The system skips the key value assignment and continues processing without specific key setup
[Set Root Segment Key Value Set Dependent Segment Key Value]
The system initializes the SSA structure for dependent segment access → The system sets the root segment key value from GCSTBRT-KEY and sets the dependent segment key value from GCSTBDP-KEY
[Set Root Segment Key Value Change SSA Type to Unqualified]
The system initializes the SSA structure for dependent segment access → The system sets the root segment key value from GCSTBRT-KEY and changes the SSA flag to unqualified SSA
[Set Root Segment Key Value Change SSA Type to Unqualified]
The system initializes the SSA structure for dependent segment access → The system sets the root segment key value from GCSTBRT-KEY and ensures the SSA flag is set to unqualified SSA
[Set Root Segment Key Value]
The system initializes the SSA configuration → The system sets both the root segment key value from GCSTBRT-KEY and the dependent segment key value from GCSTBDP-KEY
[Use Alternative SSA Configuration]
The system initializes the SSA configuration → The system sets only the root segment key value from GCSTBRT-KEY and changes the SSA flag to unqualified
[Use Alternative SSA Configuration]
The system initializes the SSA configuration → The system sets the root segment key value from GCSTBRT-KEY and ensures the SSA flag is set to unqualified
[Set Root Key Value]
SSA initialization is performed → Root key value is set from GCSTBRT-KEY AND dependent key value is set from GCSTBDP-KEY
[Set Root Key Value Only]
SSA initialization is performed → Root key value is set from GCSTBRT-KEY AND SSA type is changed to unqualified
[Set Root Key Value]
SSA initialization is performed → Root key value is set from GCSTBRT-KEY AND SSA type is set to unqualified
[Is SSA Type Qualified?]
If the SSA flag type → The system determines if the SSA type is qualified or not
[Is Unqualified Flag Set?]
The system checks the unqualified SSA flag status → The system determines if the unqualified flag is set (not space) or not set (space)
[Set Root Key Value, Set Dependent Key Value, Keep Qualified SSA Type]
The system configures the SSA parameters → The system sets both root key value and dependent key value while maintaining qualified SSA type
[Set Root Key Value Only, Change to Unqualified SSA Type]
The system configures the SSA parameters → The system sets only the root key value and changes the SSA type to unqualified
[Is SSA Type Unqualified?]
If the SSA flag type → The system determines if the SSA type is unqualified
[Set Root Key Value, Force Unqualified SSA Type]
The system configures the SSA parameters → The system sets the root key value and forces the SSA type to unqualified
[Route to Primary PCB]
The second PCB flag is spaces (not set) → The system routes the request to primary PCB processing (B310-ACCESS-ROOT-PCB1)
[Route to Secondary PCB]
The second PCB flag is not spaces (is set) → The system routes the request to secondary PCB processing (B320-ACCESS-ROOT-PCB2)
[Execute Database Call with Qualified SSA]
The database call is executed for root segment using primary PCB → The system calls the database interface with qualified root segment search arguments to retrieve specific records
[Execute Database Call with Unqualified SSA]
The database call is executed for root segment using primary PCB → The system calls the database interface with unqualified root segment search arguments to retrieve records without specific criteria
[Execute Database Call without SSA]
The database call is executed for root segment using primary PCB → The system calls the database interface without any segment search arguments
[SSA Type Check]
The SSA type needs to be determined for the database operation → The system checks the WS-SSA-FLAG to determine whether to use qualified SSA, unqualified SSA, or no SSA for the database call
[Execute Database Call with Qualified SSA]
A database operation is requested on the root segment → Execute database call using secondary PCB with qualified root segment search arguments
[Execute Database Call with Unqualified SSA]
A database operation is requested on the root segment → Execute database call using secondary PCB with unqualified root segment search arguments
[Execute Database Call with No SSA]
A database operation is requested on the root segment → Execute database call using secondary PCB without any search arguments
[Execute Database Call with Qualified SSA]
A database operation is requested for dependent segment access → The system calls the database interface with the secondary PCB, user function code, segment data, and both qualified root and dependent SSA parameters
[Execute Database Call with Unqualified SSA]
A database operation is requested for dependent segment access → The system calls the database interface with the secondary PCB, user function code, segment data, qualified root SSA, and unqualified dependent SSA parameters
[Execute Database Call with No SSA]
A database operation is requested for dependent segment access → The system calls the database interface with only the secondary PCB, user function code, and segment data parameters
[Check PCB Selection Flag]
The system checks the second PCB flag status → If the second PCB flag is spaces (not set), route to primary PCB processing, otherwise route to secondary PCB processing
[Route to Primary PCB]
The system routes the operation → The operation is directed to the primary PCB dependent segment processing routine
[Route to Secondary PCB]
The system routes the operation → The operation is directed to the secondary PCB dependent segment processing routine
[Execute Dependent Segment Operation via Primary PCB]
The system executes the database operation → Call the database interface with primary PCB, function code, segment data, qualified root SSA, and qualified dependent SSA
[Execute Dependent Segment Operation via Primary PCB]
The system executes the database operation → Call the database interface with primary PCB, function code, segment data, qualified root SSA, and unqualified dependent SSA
[Execute Dependent Segment Operation via Primary PCB]
The system executes the database operation → Call the database interface with primary PCB, function code, and segment data only
[Execute Dependent Segment Operation via Secondary PCB]
The system executes the database operation → Call the database interface with secondary PCB, function code, segment data, qualified root SSA, and qualified dependent SSA
[Execute Dependent Segment Operation via Secondary PCB]
The system executes the database operation → Call the database interface with secondary PCB, function code, segment data, qualified root SSA, and unqualified dependent SSA
[Execute Dependent Segment Operation via Secondary PCB]
The system executes the database operation → Call the database interface with secondary PCB, function code, and segment data only
[Check Operation Status]
The system checks the operation status code → If the status code is spaces, set return flag to successful, otherwise set return flag to unsuccessful
[Execute Database Call with Qualified SSA - Root Segment SSA - Dependent Segment SSA]
The database call is executed → The system calls the database interface with the function code, primary PCB, segment data, root segment qualified SSA, and dependent segment qualified SSA
[Execute Database Call with Unqualified SSA - Root Segment SSA - Unqualified Dependent SSA]
The database call is executed → The system calls the database interface with the function code, primary PCB, segment data, root segment qualified SSA, and dependent segment unqualified SSA
[Execute Database Call with No SSA - No SSA Parameters]
The database call is executed → The system calls the database interface with only the function code, primary PCB, and segment data without any SSA parameters
[SSA Type?]
The system checks the SSA flag value → The system routes to qualified SSA call if flag equals qualified SSA, routes to unqualified SSA call if flag equals unqualified SSA, or routes to no SSA call for any other value
[Execute Database Call with Qualified SSA]
The system determines the SSA type for database call execution → The system calls the database interface with both root segment qualified SSA and dependent segment qualified SSA parameters
[Execute Database Call with Unqualified SSA]
The system determines the SSA type for database call execution → The system calls the database interface with root segment qualified SSA and dependent segment unqualified SSA parameters
[Execute Database Call with No SSA]
The system determines the SSA type for database call execution → The system calls the database interface without any SSA parameters, using only basic operation parameters
[Execute Database Call with Qualified SSA]
The database call is executed for dependent segment access → The system calls the database interface with secondary PCB, function code, segment data, root segment SSA, and dependent segment SSA
[Execute Database Call with Unqualified SSA]
The database call is executed for dependent segment access → The system calls the database interface with secondary PCB, function code, segment data, root segment SSA, and dependent segment unqualified SSA
[Execute Database Call with No SSA]
The database call is executed for dependent segment access → The system calls the database interface with secondary PCB, function code, and segment data only
[Execute Database Call with Qualified SSA]
Database call is executed for dependent segment operation → System calls CIMS with user function code, secondary PCB, segment data, root qualified SSA, and dependent qualified SSA
[Execute Database Call with Unqualified SSA]
Database call is executed for dependent segment operation → System calls CIMS with user function code, secondary PCB, segment data, root qualified SSA, and dependent unqualified SSA
[Execute Database Call with No SSA]
Database call is executed for dependent segment operation → System calls CIMS with user function code, secondary PCB, and segment data only

Structural Validations

[Is Segment GCSTBDP?]
The system checks the segment type → The system identifies whether it is a dependent segment (GCSTBDP-KEY-NAME) or not
[Invalid Segment - Set Error Flag]
The system processes the segment → The system sets the return flag to indicate an invalid segment error

As an EDI Gateway Service,
I want to orchestrate and execute all GCCUSIO EDI data mapping and validation logic,
So that I can ensure strict compliance with US Customs (P140) automated payload constraints in a single consolidated service.

Prerequisites & Setup

[Initialize N9 Counter to Zero]
The system begins processing N9 reference segments → The system initializes the N9 counter to zero to start processing from the first segment
[Initialize N9 Counter to Zero]
The system begins processing individual N9 reference entries → The system initializes a counter to zero to track the current N9 entry position

Core Acceptance Criteria

[1:Parameter Validation]
The function code is not GU (Get Unique) → The system rejects the request with error code 0012 and message 'INVALID FUNCTION CODE'
[Segment Type?]
The segment type is GCSUSRT, GCSA2RT, GCSA8RT, or GCST2RT → The system routes to primary, secondary, message, or table processing respectively
[12:GCSA8RT Message Processing]
A record with the same key already exists, perform replace operation; if no existing record, perform insert operation → The system executes the appropriate database operation and restructures the message data format
[16:Reference Number Processing]
N9 reference segments exist for the cargo with qualifier 'CN' → The system extracts the reference number as shipment ID for the notification
[19:Station Code Processing]
The system needs to resolve location codes to station numbers → The system retrieves station information from GCSTBRT table segments using location ID
[Extract Road Number from RT082]
The system processes waybill index fields → The road number is extracted from the RT082 transportation segment
[Extract Station Number from RT082]
The system processes waybill index fields → The station number is extracted from the RT082 transportation segment
[Extract Waybill Number from RT082]
The system processes waybill index fields → The waybill number is extracted from the RT082 transportation segment
[Extract Waybill Date from RT082]
The system processes waybill index fields → The waybill date is extracted from the RT082 transportation segment
[Is Cargo Deleted?]
The cargo status indicates it has been deleted (88-GCUSRT-RT10-CPCARGO-DELETED is true) → The system should skip all index field population and exit the process immediately
[Is Cargo Record Deleted?]
The cargo record has deletion status flag set to true (88-GCUSRT-RT10-CPCARGO-DELETED) → The system skips all car ID index field population and exits the process immediately
[Is Cargo Deleted?]
The cargo status indicates it has been deleted (88-GCUSRT-RT10-CPCARGO-DELETED is true) → The bond index population process should be skipped and control should exit immediately
[Set Status Description to 'IMMEDIATE EXPORT']
The system processes cargo status description setting → The cargo status description field is set to 'IMED-EXP'
[Set PCB Control Block]
The system sets up the database call parameters → The appropriate PCB is assigned to the working storage PCB field based on the target segment
[Return Retrieved Data]
Data is returned from the database → The retrieved segment data is available in the GCWUSIO-IO-AREA for further processing
[Extract Border Station Number from MC Segment]
The system processes the MC segment information → The border station number is extracted from the MC segment structure
[Extract Border Station Number from MC Table]
The system processes the returned MC table segment → The border station number is extracted from the MC segment station number field
[Get Station Information from MC Table]
The system performs MC table lookup using the location ID as sequence ID → The system retrieves the corresponding station segment information from the MC table
[Set Border Station Number]
The station segment contains valid station number information → The system sets the station number as held border key and the CCN key as held border cargo key
[Extract Station Number from MC Table]
Station information is available in the MC table segment → The MC station number is extracted and prepared for border hold index key population
[New Data Empty?]
The system retrieves the existing record and evaluates the new cargo data content → If the new data contains only spaces, low-values, or underscores, the system should delete the existing record; otherwise it should insert or replace the record based on whether it exists
[Delete Secondary Record]
The system attempts to retrieve the existing record using GHU function → If the record exists (status code is not 'GE'), the system should proceed with deletion; if not found, the operation should continue without error
[Build Secondary SSA with Key]
The secondary record key is available and not empty → The system builds a qualified SSA (Segment Search Argument) using the key value for precise record location
[Map Secondary Key to Search Value]
Building SSA parameters for secondary segment access → Map the secondary key (GCSUSS00-KEY) to the database search value (GCA2-KEY-VALUE)
[Set Qualified SSA with CCN Key]
The system builds SSA parameters for database access → The system creates a qualified SSA using the CCN key value for targeted record retrieval
[Set Unqualified SSA]
The system builds SSA parameters for database access → The system creates an unqualified SSA for broader record access without key constraints
[Set Qualified SSA with Secondary Key]
The system builds SSA parameters for database access → The system creates a qualified SSA using the secondary key value for targeted record retrieval
[Set Qualified SSA with Message Key]
The system builds SSA parameters for database access → The system creates a qualified SSA using the message key value for targeted record retrieval
[Set Qualified SSA with Table Key]
The system builds SSA parameters for database access → The system assigns the table key value and creates a qualified SSA for targeted table record retrieval
[Secondary Index Key Provided?]
The system checks if a secondary index key (GCWUSIO-INDEX-SECN-KEY) is provided in the request → If secondary index key is provided, route to secondary index search processing, otherwise route to primary key search processing
[Check if Message Exists]
The delete function is initiated → First Execute a GHU (Get Hold Unique) operation to check if the message exists
[Message Found?]
The message exists in the system (status code is spaces) → Proceed with the delete operation using DLET function code
[Check if Message Exists]
The insert function is initiated → First Execute a GHU operation to check if the message already exists
[Message Found?]
The message already exists in the system (status code is spaces) → Use REPL function code to replace the existing message, otherwise use ISRT function code to insert new message
[Format Message Data]
The message data needs to be stored → Combine the GCSA8RT key with the saved IO area data to create the complete message segment
[Retrieve Message Segment]
The retrieval operation is initiated → Build qualified SSA with the message key and Execute the database call
[Separate Key from Data]
The message data needs to be returned to the caller → Extract the data portion from the complete message segment and move it to the IO area, excluding the key portion
[Structure Message for Insert/Replace]
The system processes the insert operation for GCSA8RT segment → The system extracts the message key from the input, extracts the data content, combines the key and data into a properly structured message segment, and prepares it for database storage
[Extract Data Content from Segment]
The system successfully retrieves the message segment from storage → The system extracts the data content from the retrieved segment structure and formats it for return to the calling program
[Message Operation Type?]
If the function code → The system routes to delete processing for 'DLET', insert processing for 'ISRT', or retrieval processing for 'GU' function codes
[Structure Message for Insert/Replace]
The system attempts to retrieve the existing message using GHU function → If the message exists, the system performs a replace operation; if the message does not exist, the system performs an insert operation
[Save Original IO Area]
The operation type is ISRT or REPL → The original IO area content must be saved to working storage before any modifications
[Extract Message Key from Input]
The operation is insert or replace → The message key must be extracted from the GCWUSIO input area to the working storage key field
[Extract Message Data from Input]
Processing insert or replace operations → The message data content must be extracted from the saved IO area to working storage data field
[Move Key to Working Storage Key Field]
Structuring a message segment → The key must be moved to the appropriate working storage key field
[Move Data to Working Storage Data Field]
Structuring a message segment → The data must be moved to the appropriate working storage data field
[Combine Key and Data into Segment Format]
Creating a structured segment for database operations → The key and data must be combined into the complete segment structure in working storage
[Move Structured Segment to IO Area]
Preparing for database insert or replace operation → The structured segment must be moved to the GCWUSIO IO area
[Retrieve Message Segment]
Processing GU operations with valid key → The message segment must be retrieved using the qualified SSA and appropriate PCB
[Extract Segment into Working Storage]
Processing the retrieved segment data → The complete segment must be moved to working storage for data extraction
[Move Data Portion to IO Area]
Preparing retrieval operation response → Only the data portion must be moved back to the GCWUSIO IO area
[Delete Operation Completed]
The system processes the delete request → The system retrieves the existing record first using 'GHU' function and if the record exists, deletes it using 'DLET' function with unqualified SSA
[Insert/Replace Operation Completed]
The system processes the insert request → The system first attempts to retrieve existing record with 'GHU' function, and if record exists performs 'REPL' operation, otherwise performs 'ISRT' operation with the formatted segment data
[Insert/Replace Operation Completed]
The system prepares the segment data for database operation → The system moves the GCSA8RT key to the segment key field and moves the saved IO area data to the segment data field, then moves the complete formatted segment to the IO area
[Message Data Formatted for Return]
The system successfully retrieves the record → The system moves the complete IO area to a work segment, extracts only the data portion from the work segment, and moves the extracted data back to the IO area for return
[Call Table Lookup Service]
The system needs to retrieve station information → The GCCTBIO table lookup service is called with the prepared parameters to access table segments
[Extract Station Number]
The system needs to extract station information → The table segment data is moved to MC segment structure and the MC station number is extracted for use
[Set Border Station Code via MC Table Lookup]
The MC table lookup is performed using cargo location ID name → If MC table lookup returns success flag '0', set the MC station number from table segment to error border index field AND set cargo CCN key to error border cargo field
[Set Border Hold Index via MC Table Lookup]
The cargo has US cargo hold status:
US cargo hold PCS status
US cargo pre-hold PCS status
US cargo hold border status
US cargo pre-hold border status
US cargo hold FDA status
→ Execute MC table lookup using cargo location ID name AND if lookup returns success flag '0', set MC station number from table segment to held border index field AND set cargo CCN key to held border cargo field
[Extract Border Station Number from Table]
The system processes the table lookup results → The border station number is extracted from the MC segment station number field for error index population
[Extract Border Station Number from MC Segment]
The system processes the retrieved MC table segment → The border station number is extracted from the MC segment and made available for error index population
[Set Generic Table Parameters - Function Code: 'GU' - Clear Return Flags]
The system initiates a table lookup through Z1900-GET-TABLE-SEGMENT → The system sets function code to 'GU' (Get Unique), clears all return flags and secondary PCB flags, and prepares standard calling parameters for the GCCTBIO service
[Extract Station Information - Station Number - Border Station Data]
The system processes the returned table segment data → The system extracts the relevant business data from WS-TABLE-SEGMENT into the appropriate fields such as station numbers for MC tables or notification settings for IH tables
[Retrieve Iron Highway Station Configuration]
The system needs to check Iron Highway configuration → Retrieve table segment 'IH' using the waybill station number as the sequence ID
[Extract N9 Reference Numbers]
The system processes N9 reference number segments for the cargo → Search through up to 20 N9 reference number qualifiers and extract the reference number where qualifier equals 'CN' as the shipment ID
[Send Notification to Iron Highway System]
All required notification data is available including car ID, waybill number, CCN, and status → Send notification to Iron Highway system using record type 'UC' with car identification, waybill number, cargo control number, shipment ID, and determined status
[Call Table Lookup Service]
The system calls the table lookup service → The GCCTBIO service is invoked with the configured parameters to retrieve table segment data
[Retrieve IH Station Settings]
The system processes the retrieved table segment → IH station settings are extracted and made available for notification processing
[Call Table Lookup Service]
The system needs to retrieve Iron Highway configuration data → The table lookup service should be called with the prepared parameters to retrieve the configuration segment
[Extract Station Information]
The system processes the retrieved table data → Station information is extracted from the table segment for use in subsequent processing
[Move Table Segment to Working Storage]
The system prepares to process the station data → The table segment is moved to the MC segment working storage area for further processing
[Extract Station Number]
The system needs the station number for cargo processing → The station number is extracted from the MC table segment data structure
[Extract Station Number from MC Segment]
The system processes the retrieved station data → The station number is extracted from the MC segment for use in border location processing
[Retrieve N9 Reference Data]
The system executes a database call to retrieve N9 reference data → The system retrieves the N9 reference data from the GCSA2RT secondary cargo segment
[Set Record Type to '02']
Building the access key for secondary cargo data → The system sets the record type to '02' to identify N9 reference data segments
[Set Sequence Number to '0001']
Accessing N9 reference segments in secondary cargo data → The system sets the sequence number to '0001' to retrieve the first N9 segment
[Loop Through 20 N9 Reference Segments]
Processing N9 reference segments for shipment identification → The system loops through exactly 20 N9 reference segments to examine each one
[Reference Qualifier = 'CN'?]
Examining the reference number qualifier in the current segment → The system checks if the qualifier equals 'CN' to identify shipment ID data
[Extract Shipment ID from Reference Number]
Processing the reference number field of the segment → The system extracts the reference number value as the shipment ID
[Store Shipment ID for Iron Highway]
Preparing data for Iron Highway notification → The system stores the shipment ID in the Iron Highway notification data structure
[Build Secondary Key with CCN + Record Type '02' + Sequence '0001']
The system needs to retrieve N9 reference segments from secondary cargo data → The system builds a composite key using the CCN, record type '02', and sequence '0001'
[Retrieve First N9 Segment from GCSA2RT]
The system executes a database retrieval operation against secondary cargo data → The system retrieves the first N9 reference segment if it exists
[N9 Segment Found?]
The system checks the operation result status → If segments are found, continue with N9 processing, otherwise skip N9 processing entirely
[Extract N9 Reference Numbers]
Processing N9 reference data for the cargo CCN key → Extract shipment ID from N9 reference qualifier 'CN' and store in Iron Highway message
[Prepare Iron Highway Message]
Preparing the Iron Highway notification message → Set record type to 'UC' AND set car ID from saved car number AND set waybill from saved waybill number AND set CCN from cargo CCN key
[Call Iron Highway Interface GCCIH]
Sending the notification to Iron Highway system → Call external program 'GCCIH' with common control block and Iron Highway message structure
[Exit - No Message Needed]
Both US cargo status description is empty AND CP cargo status description is empty → The system exits the notification process without sending a message
[Exit - No Change]
The saved IH status equals the current US cargo status description → The system exits the notification process without sending a message
[Exit - Release Status]
The US cargo status description equals 'RELEASE' → The system exits the notification process without sending a message
[Set Message Status to 'DELETED']
The CP cargo status description equals 'DELETED' → The system sets the Iron Highway message status to 'DELETED' and the saved IH status to 'DELETED'
[Set Message Status to 'RELEASE']
The CP cargo status description equals 'RELEASE' → The system sets the Iron Highway message status to 'RELEASE' and the saved IH status to 'RELEASE'
[Set Message Status to 'SENT']
The US cargo status description is empty AND the CP cargo status description equals 'SENT ' → The system sets the Iron Highway message status to 'SENT'
[Set Message Status from US Cargo Description]
The US cargo status description is not empty:
the CP cargo status description is not 'SENT '
→ The system sets the Iron Highway message status to the US cargo status description and updates the saved IH status to the US cargo status
[Set Message Record Type to 'UC']
The system prepares the notification message content → The system sets record type to 'UC', car ID from saved car number, waybill from saved waybill number, and CCN from cargo key
[Call Iron Highway Interface]
The system is ready to send the notification → The system calls the GCCIH program with the common control block and Iron Highway message structure
[Retrieve Secondary Cargo Data GCSUSS02 Segment]
The system executes a retrieval operation for secondary cargo data → The system calls the database interface to retrieve the GCSUSS02 segment using the qualified key
[Set Border Station from Table]
The system processes the table lookup results for border station determination → The station number is extracted from the MC table segment and assigned to the error border index field with error code 'E'
[Populate Hold Index Fields]
The system processes hold field population for border-related holds → The system performs MC table lookup using the cargo's location ID, and if successful (return flag '0'), extracts the station number from the MC table segment and assigns it to the held border index field, and assigns the cargo CCN key to the held border cargo index field
[Extract Border Station Number from MC Segment]
The system processes the retrieved MC table data → The border station number is extracted from the MC segment and made available for cargo status processing
[Extract Border Station Number from Table]
The system processes the table lookup response → The border station number is extracted from the MC-STATION-NUM field in the table segment and assigned to the error border key
[Use Border Station Number]
The table lookup returns successfully with return flag '0' → The system uses the retrieved station number from the table segment to set the border hold index
[Retrieve Station Information for Border]
The system needs to set border hold index → The system calls table lookup function to retrieve MC table segment using cargo location ID and extracts station number for border hold index
[Get Border Station from MC Table]
The system looks up MC table using cargo location ID → If table lookup is successful, the border station number is retrieved from the table segment
[Use Border Station Number from MC Table]
The system needs to determine the border station number → The system calls table lookup service to retrieve MC table segment using the cargo location ID and extracts the station number if lookup is successful
[Set Border Hold Index]
The cargo status is USCARGO-HOLD:
USCARGO-HOLDPCS
USCARGO-PR-HPCS
USCARGO-HOLD-B
USCARGO-PR-H-BO
USCARGO-HOLDFDA AND table lookup returns success flag '0'
→ Set the MC station number from table segment to held border key AND set the cargo CCN key to held border cargo key

Structural Validations

[1:Parameter Validation]
The segment name is not one of GCSUSRT, GCSA2RT, GCSA8RT, or GCST2RT → The system rejects the request with error code 0012 and message 'SEGMENT NAME INVALID'
[1:Parameter Validation]
The function code is not GU, GN, ISRT, REPL, or DLET → The system rejects the request with error code 0012 and message 'FUNCTION CODE INVALID'
[11:Secondary Database Processing]
The function is GU or GN and the secondary key is empty or spaces → The system returns error code 0012 with message 'SECN-KEY EQUAL SPACES'
[12:GCSA8RT Message Processing]
The function is GU or GN and the GCSA8RT key is empty or spaces → The system returns error code 0012 with message 'GCSA8RT-KEY EQUAL SPACES'
[Is Segment Name Valid?]
The segment name is not GCSUSRT and not GCSA2RT and not GCSA8RT and not GCST2RT → The parameter should be marked as invalid with error code '0012' and message 'SEGMENT NAME INVALID'
[Is Function Code Valid?]
The function code != 'GU ' and not equal to 'GN ' and not equal to 'ISRT' and not equal to 'REPL' and not equal to 'DLET' → The parameter should be marked as invalid with error code '0012' and message 'FUNCTION CODE INVALID'
[Special Validation: GCST2RT with Non-GU Function?]
The function code is not 'GU ' → The parameter should be marked as invalid with error code '0012' and message 'INVALID FUNCTION CODE'
[Log Index Inconsistency Error]
The system detects this data inconsistency condition → The system logs error message 'GCSB1RT EXIST WITHOUT GCSUSRT' and calls error handling routine
[Log Index Inconsistency Error]
The system detects this index inconsistency → The system sets error message to 'GCSB1RT EXIST WITHOUT GCSUSRT' and calls CERR error handling program
[Insert Data Valid?]
If the cargo data content for insertion → The system should only proceed with insertion if the data is not all spaces, not all low-values, and not all underscores
[Is Function GU or GN?]
The function code is GU (Get Unique) or GN (Get Next) AND the secondary key (GCSUSS00-KEY) is empty spaces → Set error code '0012' and error message 'SECN-KEY EQUAL SPACES' to indicate invalid parameters
[Return Error - Key Required]
The system attempts to build SSA parameters for database access → The system returns error code '0012' with message 'SECN-KEY EQUAL SPACES'
[Return Error - Key Required]
The system attempts to build SSA parameters for database access → The system returns error code '0012' with message 'GCSA8RT-KEY EQUAL SPACES'
[Message Key Available?]
The system checks if the GCSA8RT key field is empty (contains only spaces) → If the key is empty, set error code '0012' and error message 'GCSA8RT-KEY EQUAL SPACES', otherwise allow processing to continue
[Build Primary Secondary SSA]
The system needs to build SSA for primary key search on secondary data → If the secondary key (GCSUSS00-KEY) is spaces, set error '0012' with message 'SECN-KEY EQUAL SPACES', otherwise set GCSUSS00-KEY to GCA2-KEY-VALUE, use qualified SSA (GCA2-SSA-QUAL), and set PCB to GCA2-PCB
[Message Key Valid?]
The GCSA8RT key field is empty or contains only spaces → Return error code '0012' with message 'GCSA8RT-KEY EQUAL SPACES'
[Extract Message Key]
The message key is empty or contains only spaces → The system sets error number '0012' and error message 'GCSA8RT-KEY EQUAL SPACES' to indicate invalid key for retrieval
[Validate Key Not Spaces]
The function code is GU or GN and the message key is spaces → An error must be set indicating the key cannot be spaces
[Set Error - Key Cannot be Spaces]
Key validation fails for GU or GN operations → Error number '0012' and message 'GCSA8RT-KEY EQUAL SPACES' must be set
[Retrieve Operation Completed]
The system validates the input parameters → If the GCSA8RT key equals spaces, the system sets error number '0012' and error message 'GCSA8RT-KEY EQUAL SPACES', otherwise builds qualified SSA with the key value
[Exit - Station Not Configured]
The table lookup returns a non-zero return flag indicating the station is not found → The system exits the notification process without sending a message

As an EDI Gateway Service,
I want to orchestrate and execute all GCCADDT EDI data mapping and validation logic,
So that I can ensure strict compliance with US Customs (P140) automated payload constraints in a single consolidated service.

Prerequisites & Setup

[Initialize Database Segments]
Database segment areas need initialization → The EMTZ-ROOT-SEGMENT should be initialized to prepare for database operations
[Initialize Cargo Segment]
The system prepares to query for cargo records → The cargo segment structure is initialized to empty/default values
[Initialize Cargo Segment Structure]
The system needs to retrieve the next cargo record → The cargo segment structure must be initialized to clear any previous data
[Initialize IMS Transaction]
The system needs to send the message to export queue → IMS transaction is initialized with CHNG function and export PCB

Core Acceptance Criteria

[12:Check Bond Requirements]
Bond requirements are checked → Generate message twenty-three AND create IT export special manifest
[13:Validate Waybill Existence]
Waybill validation is performed → Generate message twenty-three AND create US-US detour special manifest
[14:Validate Cargo Export Status]
Export status is validated → Generate message twelve error
[16:Validate Port Codes]
Port codes are validated → Generate message twenty AND create change port special manifest
[18:Process Diversion Cases]
Diversion processing is initiated → Generate message twenty AND create diversion special manifest
[24:Finalize Report Processing]
Report finalization is performed → Set last report line index AND count error messages AND count warning messages AND count information messages AND process any special manifests if no errors exist
[25:Send Report to Customs]
Report transmission is initiated → Set customs user code AND set destination filename to REQUEST AND populate subject with user ID, train, and timestamp AND call EMCSEND2 to transmit report AND generate system error IF transmission fails
[26:Spawn GCX101 Processing]
Manifest spawning is performed → For each special manifest: copy manifest data to message format AND call CIMS to change to export PCB AND call WRITMSGL to write message AND call CIMS to purge export PCB
[27:Return Processing Results]
Results are returned → Return report table and CCN key array IF processing successful OR return error status IF errors occurred OR return no waybill status IF information messages exist
[Call Database Function to Get Next Cargo Record]
The system executes the next cargo retrieval operation → The database function GCCUSIO must be called with GN (Get Next) function to retrieve the next cargo record
[Set TE Bond Found Flag]
The transport record created for immediate transport flag != 'Y' → Set the TE (Transport Export) found flag to true
[Set TR Bond Found Flag]
The transport record created for immediate transport flag != 'Y' → Set the TR (Transport) found flag to true
[Bond Type = 'TR' and Status = 'EXPORT'?, Bond Type = 'TR'? AND Cargo Status = 'EXPORT'? AND Bill as CPRS? AND User Security Level NOT 'S'?]
User security level is not 'S' → Generate export security error message (MSG-TWELVE)
[Transport Export without TR Created?]
Cargo location does not match train crossing port → Generate port change message (MSG-TWENTY) and create CHG-PORT special manifest
[US-CAN-US with Master In-Bond?]
Train crossing port does not match cargo location → Generate port change message (MSG-TWENTY) and create DIVERSION special manifest
[User Security Level = S?]
User security level is not 'S' (supervisor level) → Generate export restriction error message (MSG-TWELVE)
[Determine Bond Type Required]
The cargo has transport code M1201-IMM-TRANSP → Set TR-REQ-FOR-IT flag to indicate transport bond is required for immediate transport
[Determine Bond Type Required]
The cargo has transport code M1201-TRANSP-EXPORT → Set TE-REQ-FOR-TE flag to indicate transport export bond is required
[Determine Bond Type Required]
The cargo has transport code M1109-DEFAULT → Set TR-REQ-FOR-00 flag to indicate transport bond is required for default cargo
[Determine Bond Type Required]
The cargo has transport code M1109-EXPORT → Set TE-REQ-FOR-88 flag to indicate transport export bond is required for export cargo
[Determine Bond Type Required]
The cargo has transport code M1201-US-CAN-US → Set TR-REQ-FOR-TR flag to indicate transport bond is required for US-Canada-US movement
[Generate Message 22: Missing TR Bond for IT Export]
TR bond requirement is set for IT export AND TR bond is not found → Add saved IT line to report AND set message twenty-two flag AND increment report index
[Generate Message 30: Missing TE Bond for TE Export]
TE bond requirement is set for TE export AND TE bond is not found → Add saved IT line to report AND set message thirty flag AND increment report index
[Generate Message 31: Missing TR Bond for Default]
TR bond requirement is set for default processing AND TR bond is not found → Add saved IT line to report AND set message thirty-one flag AND increment report index
[Generate Message 32: Missing TR Bond for TR Type]
TR bond requirement is set for TR type AND TR bond is not found → Add saved IT line to report AND set message thirty-two flag AND increment report index
[Generate Message 33: Missing TE Bond for 88 Export]
TE bond requirement is set for 88 export AND TE bond is not found → Add saved IT line to report AND set message thirty-three flag AND increment report index
[Generate IT Export Message]
The system processes error messages → Set MSG-TWENTY-THREE flag to TRUE AND increment report index AND set WS-GCX101-IT-EXPORT flag to TRUE
[Generate IT Export Message, Generate IT Export Message for IMM-TRANSP, Generate IT Export Message for Default]
The system processes the cargo validation → The system sets MSG-TWENTY-THREE message flag to TRUE and increments report index and sets WS-GCX101-IT-EXPORT flag to TRUE
[Generate Message 23: US-US Detour Required]
The origin country is US AND the destination country is US → Generate message MSG-TWENTY-THREE and create a US-US-DETOUR special manifest
[Generate Message 23: US-US Detour Required]
No cargo is found for the waybill → Set WS-GCX101-US-US-DETOUR flag and Execute special manifest creation with empty CCN, equipment ID, waybill root, and waybill date
[Is User Security Level NOT 'S'?]
User security level is not 'S' (supervisor level) → Generate export status error message (MSG-TWELVE)
[Does Cargo Port NOT Match Train Port?]
Cargo location port does not match train crossing port → Generate diversion message (MSG-TWENTY) AND create special manifest for port change (CHG-PORT)
[US-CAN-US Transit with Release Status?, Immediate Transit without TR?, Default Bond with Release Status?]
System processes the cargo for manifest validation → System sets message twenty-three flag AND adds report index AND sets IT export flag for GCX101 AND creates special manifest
[Transport Export with Port Mismatch?]
System processes the cargo for manifest validation → System sets message twenty flag AND adds report index AND sets port change flag for GCX101 AND creates special manifest
[US-CAN-US with Port Mismatch?]
System processes the cargo for manifest validation → System performs diversion process which sets message twenty flag AND adds report index AND sets diversion flag for GCX101 AND creates special manifest
[Set Diversion Message]
The system processes the diversion requirement → Message type MSG-TWENTY is set for the report indicating port diversion is needed
[Add Message to Report]
The system updates the processing report → The report index is incremented to include the diversion message in the output report
[Set Diversion Message]
The system processes the diversion condition → Set message twenty (MSG-TWENTY) to indicate diversion requirement
[Add Report Line]
The system updates the report → Add report index to include the diversion message in the output report
[Set GCX101 Diversion Flag]
The system prepares for manifest creation → Set WS-GCX101-DIVERSION flag to true to indicate diversion manifest type
[Generate US-to-US Detour Message]
System processes US domestic detour requirement → System sets message twenty-three flag to indicate US-to-US detour situation
[Add Message to Report]
System adds message to report → System increments report index to include the detour message in the output report
[Set US-US-Detour Flag]
System sets processing flags for special manifest creation → System sets US-US-detour flag to true to trigger appropriate manifest generation
[Generate Missing Cargo Message]
Origin country is not 'US':
destination country is not 'US'
→ System sets message fifteen flag to indicate missing cargo situation
[Add Waybill Root Key and Date to Message]
System adds waybill details to the message → System includes waybill root key and waybill date in the message fifteen content for identification purposes
[Set IT Export Type]
The manifest type is being determined as IT export → The system sets GCX101 IT export flag to true, populates equipment ID, waybill number, waybill date, and CCN from cargo
[Execute GCX101 Spawn Process]
The spawn processing is executed for each queued request → The system retrieves each spawn table entry, moves it to message format, and calls CIMS to change to export PCB
[Send Message to Export Queue]
The message is being sent to the export queue → The system calls WRITMSGL to write the message with code, content, length and module name to the export PCB
[Purge Message Queue]
The message processing is complete → The system calls CIMS with purge function to clear the export PCB queue
[Generate Message 23: IT Export Required]
The system processes the cargo validation → Set MSG-TWENTY-THREE message flag AND create IT-EXPORT special manifest request
[Generate Message 23: US-US Detour Required]
The system determines routing requirements for domestic movement → Set MSG-TWENTY-THREE message flag AND create US-US-DETOUR special manifest request
[Generate Message 20: Diversion Required]
The system processes port change requirements → Set MSG-TWENTY message flag AND create CHG-PORT special manifest request
[Generate Message 20: Diversion Required]
The system processes diversion requirements for master in-bond cargo → Execute diversion process to generate MSG-TWENTY and create DIVERSION manifest request
[Cargo Found with TR Created for IT?]
If the cargo movement type codes → Set the appropriate transport requirement flag: IT for immediate transport (M1201-IMM-TRANSP), TE for transport export (M1201-TRANSP-EXPORT), 00 for default (M1109-DEFAULT), 88 for export (M1109-EXPORT), or TR for US-Canada-US (M1201-US-CAN-US)
[US-CAN-US Cargo Released?, Immediate Transport Not Created?, Default Cargo Released?]
The system processes the cargo validation → Generate message twenty-three (IT Export Required) AND create IT export special manifest
[US-to-US Movement?]
The system determines movement is domestic US routing → Generate message twenty-three (US-US Detour) AND create US-US detour special manifest
[Export Cargo Security Issue?]
The system validates user access to export cargo → Generate message twelve (Security Level Error)
[Transport Export Port Change?]
The system validates transport export cargo routing → Generate message twenty (Port Change Required) AND create port change special manifest
[Diversion Required?]
The system validates US-Canada-US cargo routing → Generate message twenty (Diversion Required) AND create diversion special manifest
[Categorize Message Type]
The system categorizes the message type → If message is error type, increment error count OR if message is warning type, increment warning count OR if message is information type, increment information count
[US-CAN-US Cargo with Release Status?, Immediate Transport Cargo?, Default Cargo with Release Status?]
The system processes the cargo for manifest requirements → The system should set message twenty-three, increment report index, set IT export flag, and create special manifest
[Is Cargo US-CAN-US Type?, Is Cargo Default Type?]
The cargo transport record creation flag is not 'Y' AND the cargo status description is 'RELEASE' → Set message twenty-three indicator to true AND create special manifest for IT export processing
[Is Cargo Immediate Transport Type?]
The cargo transport record creation flag is not 'Y' → Set message twenty-three indicator to true AND create special manifest for IT export processing
[Set IT Export Flag to True]
Creating a special manifest → The IT export flag is set to true to classify the manifest type
[Set US-US Detour Message]
The system confirms both origin and destination are within the US → Message twenty-three should be set in the report and the report index should be incremented
[Generate Message 23: US-US Detour Required AND Set GCX101 US-US Detour Flag AND Create Special Manifest for US-US Detour]
The system processes the detour requirement → The system should generate message 23 indicating US-US detour required AND set the GCX101 US-US detour flag AND create a special manifest for US-US detour processing
[Generate Message 15: No Cargo Found for Waybill AND Include Root Key and Waybill Date in Message]
The system processes the no-cargo condition → The system should generate message 15 indicating no cargo found for the waybill AND include the root key and waybill date in the error message
[Set US-US Detour Message]
The system processes the US-US detour scenario → Message twenty-three is set in the report for the current report index
[Set Origin Country to Spaces - Not Found]
Both the origin country and destination country are determined to be 'US' → The system generates message twenty-three, creates a US-US-DETOUR special manifest, and adds it to the report
[Is Spawn Message?]
The message is identified as a spawn message → Skip updating any message type counters and proceed to increment report index
[Warning Message?]
The message is classified as a warning message type → Add 1 to the warning counter
[Information Message?]
The message is classified as an information message type → Add 1 to the information counter
[Increment Report Index]
Message type categorization is complete → Add 1 to the report index
[Set IT Export Flag]
Processing cargo for manifest requirements → Set IT export flag to true AND create IT export manifest
[Set IT Export Flag]
Processing cargo for manifest requirements → Set message twenty-three AND increment report index AND set IT export flag to true AND create IT export manifest
[Set Diversion Flag]
Processing cargo for manifest requirements → Set message twenty AND increment report index AND set diversion flag to true AND create diversion manifest
[Set Port Change Flag]
Processing cargo for manifest requirements → Set message twenty AND increment report index AND set port change flag to true AND create port change manifest
[Set US-US Detour Flag]
Processing cargo for manifest requirements → Set message twenty-three AND increment report index AND set US-US detour flag to true AND create US-US detour manifest
[Process Spawn Messages]
The system processes spawn messages → Execute spawn processing for each request from index 1 to spawn count
[Convert to Port Change Message]
A message line contains a diversion spawn message → Set message nineteen flag and populate station field with train crossing port
[Convert to IT Export Message]
A message line contains an IT export spawn message → Set message eighteen flag for the report line
[Any Info Messages?]
The system checks for informational messages → Return true if info count is greater than zero, otherwise return false
[Set Report Status to NO-WAYBILL]
The system assigns final status → Set report status to NO-WAYBILL
[Set Report Status to OK]
The system assigns final status → Set report status to OK
[Set Email Parameters]
The system prepares email parameters for transmission → The sender code is set to OM01247, recipient code is set to OM01247, destination filename is set to REQUEST, and keywords and copy user code are cleared
[Prepare Message for GCX101]
The message needs to be prepared for transmission → The input data is moved to the GCT1011E message structure
[Write Message to Export Queue]
The message needs to be sent to external system → The message is written to the export queue using WRITMSGL
[Commit IMS Transaction]
The transaction needs to be finalized → IMS transaction is committed using PURG function
[Update Message Types for Failed Spawns]
Spawn processing cannot proceed normally due to errors → The system updates message types for failed spawn processes
[Diversion Message?]
The message is identified as a diversion spawn message → The system sets the appropriate diversion error message type
[IT Export Message?]
The message is identified as an IT export spawn message → The system sets the appropriate IT export error message type
[Generate Train Arrival Warning Message]
The train has arrived AND the first report line contains no US-CCN data → Generate message twenty-six warning and add it to the report
[Count Report Statistics]
The system needs to finalize report statistics → Set the last report line index and process report wrap-up including spawn message handling
[Set Success Return Code]
The processing is successful → Set the return status to OK

Structural Validations

[11:Validate Cargo Status]
Cargo type is immediate transport → Set TR required for IT flag to true
[13:Validate Waybill Existence]
Waybill is not found → Generate message ten error
[13:Validate Waybill Existence]
Waybill validation is performed → Generate message fifteen with waybill root key and date
[14:Validate Cargo Export Status]
Export status is validated → Generate message seventeen error
[14:Validate Cargo Export Status]
Export status is validated → Generate message sixteen error
[15:Validate Train Attachment]
Train attachment is validated → Generate message twenty-five error
[22:Validate Train Arrival Status]
Train arrival status is validated → Generate message twenty-six error
[23:Generate Error Messages]
Error message generation is performed → Generate message twenty-two IF TR required for IT but not found OR generate message thirty IF TE required for TE but not found OR generate message thirty-one IF TR required for default but not found OR generate message thirty-two IF TR required for TR but not found OR generate message thirty-three IF TE required for 88 but not found
[Errors Found?]
Final result is determined → Set no waybill status IF information messages exist OR set error status and send to customs IF error messages exist OR set OK status and return report data IF no errors exist
[Generate TR Bond Missing Error]
TR bond is required for IT but TR is not found → Message twenty-two error is generated and TR requirement flag is set
[Generate TE Bond Missing Error]
TE bond is required for TE but TE is not found → Message thirty error is generated and TE requirement flag is set
[Generate Bond Requirement Errors]
TR bond is required for default transport but TR is not found → Message thirty-one error is generated
[Generate Bond Requirement Errors]
TR bond is required for US-Canada-US transport but TR is not found → Message thirty-two error is generated
[Generate Bond Requirement Errors]
TE bond is required for export transport but TE is not found → Message thirty-three error is generated
[Generate Invalid Car ID Error]
The system detects the formatting failure → An 'INVALID CAR ID' error message is generated and added to the report
[Process Error - Service Failed]
Service failure needs to be handled → Error message is constructed with service parameters and error processing is initiated to terminate the operation
[Bond Type = 'TE' and Vessel Name starts with 'T'?]
Cargo has bond type 'TE' and vessel name starts with 'T' → Generate bond vessel error message (MSG-SEVENTEEN)
[Bond Type ≠ 'TE' or 'MT' and Vessel ≠ 'TRAIN'?]
Cargo bond type is not 'TE' and not 'MT' and vessel name is not 'TRAIN' → Generate bond type error message (MSG-SEVENTEEN)
[Cargo Status = Pending/Deleted/Error?]
Cargo status is pending, deleted, or error → Generate cargo status error message (MSG-SIXTEEN)
[Bond Type = 'MT' and Vessel ≠ 'TRAIN'?]
Vessel name is not 'TRAIN' and not spaces and train crossing port does not match cargo location → Generate port mismatch error message (MSG-TWENTY-FIVE)
[Check if bond type matches vessel requirements and generate appropriate error messages]
The 23rd character of the vessel name is 'T' → Generate message seventeen indicating invalid vessel for TE bond type
[Check if bond type matches vessel requirements and generate appropriate error messages]
The vessel name != 'TRAIN' → Generate message seventeen indicating invalid vessel for bond type
[Check if bond type matches vessel requirements and generate appropriate error messages]
The train crossing port does not equal the cargo location ID → Generate message twenty-five indicating port mismatch for MT bond
[Is Bond Type = 'TE'? and Does Vessel Name Start with 'T'?]
Vessel name starts with 'T' (23rd character position) → Set message 17 flag to indicate invalid vessel configuration for TE bond
[Is Bond Type NOT 'TE' or 'MT'? and Is Vessel Name NOT 'TRAIN'?]
Vessel name != 'TRAIN' → Set message 17 flag to indicate invalid vessel name for the bond type
[Cargo Status = Pending?]
Cargo status is pending (RT10-CPCARGO-PENDING condition is true) → Generate cargo status error message (MSG-SIXTEEN)
[Cargo Status = Deleted?]
Cargo status is deleted (RT10-CPCARGO-DELETED condition is true) → Generate cargo status error message (MSG-SIXTEEN)
[Cargo Status = Error?]
Cargo status is error (RT10-CPCARGO-ERROR condition is true) → Generate cargo status error message (MSG-SIXTEEN)
[Cargo Found?]
Cargo status validation is required → The system should verify that cargo data exists before proceeding with status checks
[Status = Pending?]
The cargo status is checked against pending state → The system should identify cargo with pending status for error message generation
[Status = Deleted?]
The cargo status is checked against deleted state → The system should identify cargo with deleted status for error message generation
[Status = Error?]
The cargo status is checked against error state → The system should identify cargo with error status for error message generation
[Set Message Sixteen - Status Error]
An invalid cargo status condition is detected → The system should set message sixteen to indicate the cargo status error
[Bond Type = MT?]
Vessel name is not TRAIN and not SPACES and train crossing port does not match cargo location ID → Generate port mismatch error message (MSG-TWENTY-FIVE)
[Bond Type = TE and Transport Export?]
Cargo location does not match train crossing port → Generate diversion message (MSG-TWENTY) and create change port manifest
[Bond Type = 'TE'? AND Vessel Name Contains 'T'?]
The vessel name contains 'T' in position 23 → Generate bond type error message (MSG-SEVENTEEN)
[Bond Type NOT 'TE' or 'MT'? AND Vessel Name NOT 'TRAIN'?]
The vessel name != 'TRAIN' → Generate bond type error message (MSG-SEVENTEEN)
[Bond Type = 'MT'? AND Vessel Name NOT 'TRAIN' or SPACES? AND Train Port ≠ Cargo Port?]
Train crossing port does not equal cargo location port → Generate port mismatch error message (MSG-TWENTY-FIVE)
[TR Required but Not Found? - Generate Missing TR Bond Error]
Processing bond requirements validation → Add saved IT line to report and generate MSG-TWENTY-TWO error message
[TE Required but Not Found? - Generate Missing TE Bond Error]
Processing bond requirements validation → Add saved IT line to report and generate MSG-THIRTY error message
[TR Required but Not Found? - Generate Missing TR Bond Error]
Processing bond requirements validation → Add saved IT line to report and generate MSG-THIRTY-ONE error message
[TR Required but Not Found? - Generate Missing TR Bond Error]
Processing bond requirements validation → Add saved IT line to report and generate MSG-THIRTY-TWO error message
[TE Required but Not Found? - Generate Missing TE Bond Error]
Processing bond requirements validation → Add saved IT line to report and generate MSG-THIRTY-THREE error message
[Generate Bond Vessel Error]
The vessel name starts with 'T' (GCUSRT-M1005-VESSEL-NAME (23:1) = 'T') → The system generates message seventeen error (MSG-SEVENTEEN)
[Generate Bond Vessel Error]
The vessel name != 'TRAIN' (GCUSRT-M1005-VESSEL-NAME NOT = 'TRAIN') → The system generates message seventeen error (MSG-SEVENTEEN)
[Generate TR Bond Export Error]
The user security level is not 'S' (GCLADDIF-USER-SECURITY-LEVEL NOT = 'S') → The system generates message twelve error (MSG-TWELVE)
[Generate MT Bond Port Error]
The train crossing port does not match the cargo location (GCLADDIF-TRAIN-CROSSING-PORT NOT = GCUSRT-P401-LOCATION-ID) → The system generates message twenty-five error (MSG-TWENTY-FIVE)
[Set Bond Vessel Error Message]
The 23rd character of vessel name is 'T' → Set bond vessel error message (MSG-SEVENTEEN)
[Set Bond Vessel Error Message]
Vessel name != 'TRAIN' → Set bond vessel error message (MSG-SEVENTEEN)
[Generate MSG-TWENTY-TWO Error]
Transport bond was not found (TR-NOT-FOUND is true) → Generate MSG-TWENTY-TWO error message and add saved line to report
[Generate MSG-THIRTY Error]
Transport export bond was not found (TE-NOT-FOUND is true) → Generate MSG-THIRTY error message and add saved line to report
[Generate MSG-THIRTY-ONE Error]
Transport bond was not found (TR-NOT-FOUND is true) → Generate MSG-THIRTY-ONE error message and add saved line to report
[Generate MSG-THIRTY-TWO Error]
Transport bond was not found (TR-NOT-FOUND is true) → Generate MSG-THIRTY-TWO error message and add saved line to report
[Generate MSG-THIRTY-THREE Error]
Transport export bond was not found (TE-NOT-FOUND is true) → Generate MSG-THIRTY-THREE error message and add saved line to report
[Generate Message 10: Container without Waybill]
The waybill is not found AND the container is found → Generate message MSG-TEN indicating container exists without waybill
[Generate Message 15: No Cargo Found for Waybill]
The movement is not US to US domestic (origin country is not US:
destination country is not US)
→ Generate message MSG-FIFTEEN with waybill root key and date
[Generate Message 15: Idler Car with No Cargo]
The idler indicator is not spaces (indicating an idler car) → Generate message MSG-FIFTEEN with waybill root key and date
[Does Train Port NOT Match Cargo Port?]
Train crossing port does not match cargo location port → Generate port mismatch error message (MSG-TWENTY-FIVE)
[Does Train Crossing Port NOT Match Cargo Location?]
The train crossing port does not match the cargo's P401 location ID → Generate port mismatch error message (MSG-TWENTY-FIVE)
[Check if train has arrived and US-CCN is required for additions]
The train has arrived AND the first US-CCN entry in the report is empty (spaces) → Generate error message MSG-TWENTY-SIX indicating train arrived but no US-CCN available for additions AND add the error to the report
[Generate Message 10: Container Waybill Missing]
The system validates waybill and container relationship → Set MSG-TEN message flag to indicate container waybill is missing
[Generate Message 15: No Cargo Found]
The system validates cargo existence for the waybill → Set MSG-FIFTEEN message flag AND populate message with ROOT-KEY and WB-DATE
[Generate Message 17: Invalid Bond Type]
The system validates transport bond type compatibility → Set MSG-SEVENTEEN message flag to indicate invalid bond type for train transport
[Generate Message 16: Cargo Status Error]
The system validates cargo processing status → Set MSG-SIXTEEN message flag to indicate cargo status error
[Generate Message 12: Security Level Error]
The system validates user authorization for export cargo processing → Set MSG-TWELVE message flag to indicate insufficient security level
[Generate Message 25: Port Mismatch]
The system validates port location for MT transport → Set MSG-TWENTY-FIVE message flag to indicate port mismatch
[Generate Message 1: No Waybill Found]
The system searches for waybill and container information → Set MSG-ONE message flag to indicate no waybill found for the equipment
[No Waybill for Container?]
The system validates waybill and container relationship → Generate message ten (Container Waybill Missing)
[No Cargo for Loaded Equipment?]
The system processes cargo validation for loaded equipment → Generate message fifteen (No Cargo Found) with waybill root key and date
[Invalid Bond Type for Vessel?]
The system validates bond type and vessel name combination → Generate message seventeen (Invalid Bond/Vessel)
[Cargo Status Error?]
The system validates cargo processing status → Generate message sixteen (Cargo Status Error)
[Port Mismatch for MT Bond?]
The system validates MT bond cargo routing → Generate message twenty-five (Port Mismatch)
[Set Origin Country to Spaces - Not Found]
Either the origin country or destination country is not 'US' → The system generates message fifteen with the waybill root key and date in the report
[Error Message?]
The message is classified as an error message type → Add 1 to the error counter
[Report Maximum Reached?]
The report index reaches the maximum allowed report lines → Set message nine indicating maximum report capacity reached
[Train Arrived and No US-CCN Found?]
Train arrival flag is set to true AND the first report line US-CCN field is empty → Add message twenty-six warning to the report and increment report index
[Email Send Successful?]
If the email return status → If transmission failed, the system processes an email send error, otherwise continues with normal processing
[Set Diversion Error Message]
The message type needs to be updated → The system sets MSG-NINETEEN with the train crossing port information
[Set IT Export Error Message]
The message type needs to be updated → The system sets MSG-EIGHTEEN for the IT export error condition
[Set Error Return Code]
The report error count is greater than zero → Set the return status to ERRORS AND send the report to customs identification

As an EDI Gateway Service,
I want to orchestrate and execute all GCCU358T EDI data mapping and validation logic,
So that I can ensure strict compliance with US Customs (P140) automated payload constraints in a single consolidated service.

Prerequisites & Setup

[Initialize Root Segment Structure / Set Transaction Set to 358]
The system initializes the EDI root segment → The root segment structure is cleared and the transaction set is set to '358'
[Initialize M10 Manifest Header]
The system begins creating the M10 manifest header segment → The M10 segment is initialized with empty values to prepare for data population
[Initialize P4 Segment]
The P4 processing begins → The P4 segment structure is initialized to clear any previous data
[Initialize VID Segment]
VID segment processing begins → VID segment structure is cleared and ready for data population
[Initialize MBL Segment]
A new MBL segment needs to be created for cargo → The system initializes the MBL segment structure and sets the identifier to 'MBL'
[Initialize N9 Segment]
The N9 segment processing begins → The system should initialize the N9 data structure to clear any previous values
[Initialize Delete Message Structure]
The delete transaction process is initiated → The delete message structure GCX112-INPUT is initialized to spaces

Core Acceptance Criteria

[Valid Bills or Valid Port?]
The system checks if BOL quantity is greater than 0 or if port is valid → Proceeds with EDI processing if either condition is true, otherwise skips to logging
[5:Generate Transmission Number]
The system generates a transmission number → Uses prefix 106 for foreground or 003 for background, combined with machine time
[6:Create EDI Root Segment]
The system creates the root segment → Inserts transmission record with transaction set '358' and generated transmission number
[7:Build M10 Manifest Header]
The system builds the M10 segment → Sets SCAC to 'CPRS', transport type to 'R', country to 'CA', manifest type to 'K' for export trains with valid port or 'S' for others, and application type '28' for export trains with valid port
[8:Build P4 Port Information]
The system builds the P4 segment → Includes origin station code, estimated arrival date with century calculation, BOL quantity, arrival time, and FIRMS code
[9:Process Equipment VID Segments]
The system processes each unique equipment ID → Creates VID segment with equipment type, initial, number (using cargo car number if available), and load/empty status (E if train shows H, L if train shows E but cargo weight > 1, otherwise train value)
[10:Process Bill of Lading MBL Segments]
The system creates MBL segment → Uses cargo-derived SCAC and BOL for valid ports, otherwise uses train list values, and sets automated response based on SCAC table lookup or special handling for empty cars with BOL type '23'
[11:Process N9 Reference Segments]
The system processes N9 segment → Creates N9 segment with reference qualifier 'IB' and entry number from cargo record
[12:Update Train Status to SENT]
The system updates train status → Sets train status to SENT, enables EDI sending flag, and updates both train database and train list
[13:Update Train Status to ACK]
The system updates train status → Sets train status to ACK and determines EDI action based on previous EDI send flag
[Delete Required?]
The system checks previous EDI send flag → Sets delete required flag if previously marked to send EDI, otherwise sets do not send EDI flag
[15:Start EDI Send Function]
The system starts EDI send function → Calls EDI send function with high-value security and generated transmission number
[16:Log Transaction Activity]
The system logs the transaction → Uses foreground or background action codes, includes user ID, date, time, and appropriate message based on cargo validity
[17:Process AEI Train Send]
The system processes AEI train send → Initiates customs transaction with train information for AEI processing
[21:Check Automated Carrier Status]
The system checks automated carrier status → Sets response to 'Y' if SCAC is 'CPRS' or if SCAC table indicates automated carrier, otherwise sets to 'N', with special 'Y' setting for empty cars with BOL type '23'
[AEI Train Send Check?]
The system checks AEI train send eligibility → Proceeds with AEI processing if train is in background mode and meets AEI criteria
[Has Valid Cargo?]
The system determines final status → Updates to SENT status if BOL quantity > 0 or port is valid, otherwise updates to ACK status
[Set Processing Mode as Valid]
GCWU358T-FOREGROUND:
GCWU358T-BACKGROUND is true
→ The system proceeds with EDI processing workflow including information gathering, root processing, and equipment processing
[Check Bond Type and Export Criteria]
Determining if cargo qualifies for BOL counting → Cargo qualifies if in-bond type is 'TR' OR if cargo type is export/returned US goods/empty residue/transport export/immediate export/multi-port AND the port is valid
[M1201 Immediate Export?]
The system continues evaluating M1201 export criteria → If cargo has M1201 immediate export classification, it qualifies for export processing subject to valid port requirement
[M1201 Immediate Export?]
The M1201 in-bond type code indicates immediate export (88-GCUSRT-M1201-IMM-EXPORT condition is true) → The cargo qualifies for export processing
[Set Prefix to 106 Foreground Mode / Set Prefix to 003 Background Mode]
The system determines the processing mode (foreground or background) → The transmission prefix is set to 106 for foreground mode or 003 for background mode
[Get Current Machine Time as Base Number]
The system needs to create a unique transmission number → The current machine time is retrieved and used as the base number component
[Combine Prefix + Time to Create Transmission Number]
The system constructs the transmission number → The prefix and machine time are combined to form the complete transmission number
[Attempt to Insert Transmission Number]
The system attempts to insert the transmission record → A new transmission record is created with transaction set '358' and the generated transmission number
[Set Transmission Prefix to 106 Foreground Mode / Set Transmission Prefix to 003 Background Mode]
The processing mode is foreground → The transmission prefix is set to 106, and when the processing mode is background, the transmission prefix is set to 003
[Generate Transmission Number Using Machine Time]
The system needs to generate a transmission number → The machine time is retrieved and combined with the prefix to create the transmission number
[Insert Successful? / Increment Transmission Number / Retry Insert with New Number]
The insertion fails due to a duplicate transmission number → The transmission number is incremented by 1 and the insertion is retried until a unique number is found
[Insert Root Segment into EDI Database]
The system attempts to insert the root segment → The root segment is stored in the EDI work database using the transmission number as the key
[Set Standard M10 Fields - Identifier: M10, SCAC: CPRS, Transport Type: R, Country: CA]
The system sets the standard transport fields → The identifier is set to 'M10', SCAC code is set to 'CPRS', transport type code is set to 'R' for rail, and country code is set to 'CA' for Canada
[Insert M10 Segment into EDI Transmission]
The system processes the segment for EDI transmission → The M10 segment is inserted into the EDI transmission data with an incremented sequence number
[Set P4 Identifier]
The segment identifier needs to be set → The identifier is set to 'P4' to indicate this is a port information segment
[Set Departure Port Location]
The P4 segment departure port needs to be populated → The departure port location is set to the train's origin station code
[Get Estimated Departure Date]
The P4 segment date field needs to be populated → The estimated departure date is extracted from the train's EDA field
[Set Bill of Lading Quantity]
The P4 segment quantity field needs to be populated → The quantity is set to the calculated bill of lading count
[Set Estimated Departure Time]
The P4 segment time field needs to be populated → The time is set to the train's estimated time of arrival (ETA) value
[Set FIRMS Code]
The P4 segment ID code field needs to be populated → The ID code is set to the train's FIRMS code value
[Insert P4 Segment into EDI]
The segment needs to be added to the EDI transmission → The P4 segment is inserted into the transmission data structure
[Set VID Identifier to 'VID']
Segment identifier needs to be set → VID identifier is set to 'VID'
[Get Equipment Type from Train List]
Equipment type data is required for VID segment → Equipment type is retrieved from train list at current equipment index and assigned to VID equipment description code
[Get Equipment Initials from Train List]
Equipment initials are required for VID segment → Equipment initials are retrieved from train list at current equipment index and assigned to VID equipment initials
[Car Number Available in Cargo?]
Car number from cargo record is not empty → Car number from cargo record is used for VID equipment number
[Use Original Load/Empty Status]
No special status conversion rules apply → Original load/empty status from train list is used for VID segment
[Insert VID Segment to EDI Data]
VID segment is ready for transmission → VID segment is inserted into EDI transmission data stream
[Valid Port?]
The port is valid → The system extracts SCAC code and BOL number from the MBL export key structure
[Extract SCAC and BOL from Equipment Data]
The port is not valid → The system extracts SCAC code from equipment SCAC field and BOL number from equipment CCN ID field
[SCAC = 'CPRS'?]
The SCAC code equals 'CPRS' → The system sets the automated carrier response code to 'Y'
[Lookup SCAC in SS Table]
The SCAC code is not 'CPRS' → The system initializes SCAC table key with 'SS' table ID, equipment SCAC code, and origin port code, then performs SCAC table lookup
[Empty Equipment with BOL Type 23?]
The equipment load/empty status is 'E' and has associated cargo with BOL type code '23' → The system overrides the automated carrier response code to 'Y'
[Insert MBL Segment to EDI]
The MBL segment is ready for transmission → The system moves the MBL segment to transmission data and inserts it into the EDI stream
[Is Carrier CPRS?]
The carrier SCAC code equals 'CPRS' → Set the MBL response code to 'Y' for automated processing
[Is Bill Transportation Export?]
The system processes the cargo record and the bill of lading type is transportation export (88-GCUSRT-M1201-TRANSP-EXPORT condition is true) → The system should proceed to create an N9 reference segment
[Set Reference Number Qualifier to 'IB']
The system populates the reference number qualifier field → The reference number qualifier should be set to 'IB' to indicate in-bond reference
[Set Entry Number from Cargo Record]
The system populates the reference number field → The entry number from the cargo record (GCUSRT-M1202-ENTRY-NUM) should be assigned to the N9 reference number field
[Insert N9 Segment into EDI Data]
The system processes the completed N9 segment → The N9 segment should be moved to the transmission data area and inserted into the EDI data stream
[Set Train Status to SENT]
The system processes the train for EDI transmission → The train status is set to SENT to indicate successful processing eligibility
[Set Train Send EDI Flag to TRUE]
The system configures transmission settings → The EDI send flag is set to TRUE to enable electronic data interchange transmission
[Set Train Status to ACK]
If the train for processing → The train status is set to ACK to indicate acknowledgment without transmission
[Previously Marked to Send?]
The system determines final EDI configuration → The system checks if the train was previously marked to send EDI transmissions
[Set Delete Required Flag]
The system finalizes train disposition → The delete required flag is set to TRUE to trigger train record cleanup
[Set Do Not Send EDI Flag]
The system finalizes EDI configuration → The do not send EDI flag is set to TRUE to prevent transmission attempts
[Update Train Record]
The system completes status processing → All changes are saved to the train record in the database
[Has Valid Bills of Lading OR Valid Port?]
If transmission requirements → The system proceeds with EDI transmission if bill of lading count is greater than zero OR port is valid
[Set Train Status to SENT Mark for EDI Transmission]
The system determines EDI transmission is required → The system sets train status to SENT and marks train for EDI transmission
[Set Train Status to ACK No Transmission Required]
The system determines no EDI transmission is required → The system sets train status to ACK indicating no transmission required
[Was Train Previously Marked for EDI Send?]
If previous EDI send configuration → The system checks if train was previously marked to send EDI
[Mark Train for Deletion Set DELETE-REQUIRED Flag]
The system determines train configuration has changed → The system sets DELETE-REQUIRED flag to mark train for deletion process
[Set Train to DO-NOT-SEND-EDI]
The system determines train should not send EDI → The system sets train configuration to DO-NOT-SEND-EDI
[Has Valid Bills of Lading or Valid Port?]
The system checks if the train has valid bills of lading greater than zero:
operates through a valid port
→ The system determines whether the train qualifies for EDI processing
[Set Train Status to SENT]
The system processes the train status update → The train status is set to SENT, EDI sending is enabled, and both train list and train root records are updated accordingly
[Was Train Previously Set to Send EDI?]
If the train's previous EDI send configuration → The system determines whether the train was previously marked to send EDI
[Mark Train for Deletion Required]
The system updates the train's EDI configuration → The train is marked as deletion required in both train list and train root records
[Set Train to Do Not Send EDI]
The system updates the train's EDI configuration → The train is marked as do not send EDI in both train list and train root records
[Update Train Status in Database]
The system performs the database update operation → The train root segment is replaced in the database with the new status information
[Trigger Train Deletion Process]
The system initiates cleanup processes → The GCT1121E deletion process is spawned to handle removal of associated EDI transmission records
[Set EDI Send Function Name]
The EDI send function process is started → The system sets the EDI send function name identifier to TRUE
[Change to EDI Send Function]
The system needs to change processing context → The system performs the function change operation to switch to EDI send context
[Set Security to High Values]
Security parameters need to be established → The system sets the security byte to HIGH-VALUES for maximum security
[Set Transmission Number]
The EDI message is being prepared for transmission → The system assigns the working storage transmission number to the EDI message transmission number field
[Prepare EDI Send Message]
The EDI message needs to be formatted for transmission → The system moves the EDI input structure to the message output text field
[Insert and Purge Message]
The message is ready for transmission → The system performs the insert and purge message operation to complete the EDI transmission
[Has Valid Bills or Valid Port?]
Message type needs to be determined for logging → System should check if bill of lading quantity is greater than zero or if port is valid
[Set Success Message - Blank]
Success message needs to be set → Log message should be set to blank spaces indicating successful processing
[Processing Mode for No Cargo?]
Processing mode needs to be determined for message assignment → System should check if transaction is running in foreground mode for no cargo scenario
[Set Train Updated Message]
Train updated message needs to be set → ZZZ train update message should be assigned to the log entry
[Set Train Added Message]
Train added message needs to be set → ZZZ train added message should be assigned to the log entry
[Send Log Message to System]
Log message needs to be sent to system → Log input should be moved to message output and log update function length should be set and message should be sent via purge message process
[Write Message to Queue]
The system queues the message for processing → The system must write the message to the queue using WRITMSGL with message code 'S'
[Convert Equipment Number to Standard Format]
Processing equipment for Canadian customs transmission → The equipment number is converted to 6-digit car number format and stored in the Canadian output table
[Convert to 6-Digit Car Number Format]
Converting to Canadian transmission format → The equipment number is formatted as a 6-digit car number
[Store Converted Number in Canadian Output Table]
Storing converted car number for Canadian transmission → The 6-digit car number is stored in the Canadian customs output table at the current equipment position
[Set Train ID in Delete Message]
Setting the train identifier in the delete message → The train's US customer train ID is moved to the GCX112-TRAIN-OR-US-CCN field
[Set Security Byte to High Value]
Setting security authorization for the delete transaction → The security byte GCX112-SECURITY-BYTE is set to HIGH-VALUE for maximum authorization
[Set Action Code to 'TD' - Train Delete]
Setting the action code for train deletion → The action code GCX112-ACTION-CODE is set to 'TD' to indicate train delete operation
[Set Train Type Indicator to US Train]
Setting the train type indicator → The train type indicator GCX112-US-TRAIN is set to TRUE
[Prepare Delete Message for GCT1121E]
Preparing the message for transaction processing → The complete GCX112-INPUT structure is moved to GCT1121E-MSG for processing
[Change to Alternative PCB]
Initiating the delete transaction processing → The system changes to the alternative PCB using CHNG function with ALT-PCB
[Send Delete Message to Message Queue]
Sending the delete message for processing → The delete message is written to the message queue using WRITMSGL with the prepared message structure
[Purge Message from Queue]
Completing the delete transaction processing → The message is purged from the queue using PURG function with ALT-PCB
[Export Type Valid?]
If the cargo type codes → The system determines if the cargo is classified as Export, Returned US Goods, Empty Residue, Transport Export, Immediate Export, or Multi-Port
[Equipment Load/Empty Status = 'H'?]
The equipment's load/empty status in the train list is 'H' (Hold) → The VID segment load/empty status code is set to 'E' (Empty)
[Has Cargo AND Status = 'E' AND Weight > 1?]
The associated cargo record shows a weight greater than 1 → The VID segment load/empty status code is set to 'L' (Loaded)
[Keep Original Status]
The equipment either has no cargo, status is not 'E', or cargo weight is 1 or less → The VID segment load/empty status code is set to the original value from the train list
[Create VID Segment with Equipment Details]
Processing equipment for VID segment creation → A VID segment is created with equipment type, initial, number, and load/empty status code
[Insert VID Segment to EDI]
The VID segment is ready for transmission → The VID segment is inserted into the EDI transmission data structure

Structural Validations

[Number Already Exists? / Increment Number by 1]
The transmission number already exists in the system → The transmission number is incremented by 1 and insertion is attempted again until a unique number is found
[Set Message Length]
The message length needs to be established → The system sets the EDI send function length indicator to TRUE
[Is Immediate Export?]
The in-bond type code indicates immediate export → Proceed to validate port authorization for cargo acceptance

As an EDI Gateway Service,
I want to orchestrate and execute all CCISCOM EDI data mapping and validation logic,
So that I can ensure strict compliance with US Customs (P140) automated payload constraints in a single consolidated service.

Prerequisites & Setup

None explicitly identified in logic extraction.

Core Acceptance Criteria

[9:CCCOM Initialization]
First time ISCOM to CCCOM conversion is performed → Transfer CC-COMMON-AREA from ISCOM to CCCOM directly without intermediate default value assignment

Structural Validations

None explicitly identified in logic extraction.

As an EDI Gateway Service,
I want to orchestrate and execute all CERR EDI data mapping and validation logic,
So that I can ensure strict compliance with US Customs (P140) automated payload constraints in a single consolidated service.

Prerequisites & Setup

None explicitly identified in logic extraction.

Core Acceptance Criteria

[Display Footer Line: Hash Border]
The error notification footer display is executed → The system displays a hash border footer line '###########################################' to the system error output (SYSERR)

Structural Validations

[7:Error Notification - Display Blocking Error Message]
The program reaches the error notification stage → The system displays blocking error message '# CIMS: BLOCKING ERROR.' to the system error output
[Skip Error Handler Routing - Proceed Directly to Error Notification]
The dump-only indicator (WS-DUMP-ONLY) is set to True → The system skips the environment detection logic and does not invoke either CERRPROD (production error handler) or CERRTEST (test error handler), proceeding directly to program termination
[Display Main Message: CIMS BLOCKING ERROR]
The main error message display is executed → The system displays the message '# CIMS: BLOCKING ERROR.' to the system error output (SYSERR)
[Error Notification Complete]
The complete error notification sequence is executed → The system displays the complete formatted error message consisting of header border, main error message 'CIMS: BLOCKING ERROR', and footer border, all directed to system error output (SYSERR) for immediate operator visibility

As an EDI Gateway Service,
I want to orchestrate and execute all CIMS EDI data mapping and validation logic,
So that I can ensure strict compliance with US Customs (P140) automated payload constraints in a single consolidated service.

Prerequisites & Setup

None explicitly identified in logic extraction.

Core Acceptance Criteria

[3:PCB Address Resolution]
Address area validation occurs → The first 8 bytes of the address area are cleared to spaces
[6:IMS Database Call Execution]
Database call is executed → The database interface is invoked with the function code, PCB copy, IO area, and up to 6 segment search arguments (SSA1 through SSA6)
[9:PCB Status Information Update]
Status information update occurs → The PCB copy is stored in the communication area's PCB copy field, and if the segment level is not '98' or '99', the feedback key length is stored in the communication area's length feedback key field
[5 or More Arguments?]
The argument count is 5 or more → The first Segment Search Argument (SSA1) is captured from the fifth argument position and stored in the Last SSA1 field of the communication area
[6 or More Arguments?]
The argument count is 6 or more → The second Segment Search Argument (SSA2) is captured from the sixth argument position and stored in the Last SSA2 field of the communication area
[7 or More Arguments?]
The argument count is 7 or more → The third Segment Search Argument (SSA3) is captured from the seventh argument position and stored in the Last SSA3 field of the communication area
[8 or More Arguments?]
The argument count is 8 or more → The fourth Segment Search Argument (SSA4) is captured from the eighth argument position and stored in the Last SSA4 field of the communication area
[9 or More Arguments?]
The argument count is 9 or more → The fifth Segment Search Argument (SSA5) is captured from the ninth argument position and stored in the Last SSA5 field of the communication area
[10 or More Arguments?]
The argument count is 10 or more → The sixth Segment Search Argument (SSA6) is captured from the tenth argument position and stored in the Last SSA6 field of the communication area
[Search Index <= 249?]
A database name entry at position I contains spaces → The search loop terminates immediately regardless of the current index value
[Call CBLTDLI Interface]
The system invokes the CBLTDLI interface with the function code, PCB reference, IO area, and all provided SSA parameters (SSA1 through SSA6) → The IMS database operation is executed and control returns with the operation result reflected in the PCB status code and any retrieved or updated data in the IO area
[Copy Key Feedback Length to Common Area]
The segment level = '98':
the segment level = '99'
→ The key feedback length is not copied to the common area and processing continues without storing key length information
[Status Code is Invalid]
No match was found between CC-STATUS-CODE of CCCOM and any entry in CC-ACC-STATUS-TAB of CCCOM → The system constructs an error message by concatenating CC-STATUS-CODE of CCCOM with the text ': IMS RC CODE NOT IN ACCEPTABLE LIST' and stores it in CC-ERROR-MESSAGE of CCCOM, then calls the error handler program 'CERR' using CCCOM and executes GOBACK

Structural Validations

[PCB Address Provided?]
Address area validation occurs → The address area is set to the default CSI address area, PCB name is set to zero, PCB number is set to zero, an error message 'Zero PCB Address Error' is set in the communication area, and the error handler is invoked
[13:Error Handling for Missing PCB Address]
PCB address validation occurs → The PCB name and number are captured, an error message 'Zero PCB Address Error' is set in the communication area, and the error handler is invoked
[12:Error Handling for Invalid Status]
Status code validation completes → An error message is formatted as '[Status Code]: IMS RC CODE NOT IN ACCEPTABLE LIST' and stored in the communication area's error message field, and the error handler is invoked
[Generate Missing PCB Error Message]
The PCB address remains NULL after the search process → The system generates an error message containing the PCB name and PCB number, stores it in the communication area error message field, and invokes the error handler program 'CERR'
[Copy Key Feedback Length to Common Area]
The segment level != '98' AND the segment level != '99' → The key feedback length from the PCB is copied to the common area's key length field for use in subsequent key-based operations
[Build Error Message with Status Code]
The system needs to report the error condition → The system uses STRING operation to concatenate CC-STATUS-CODE of CCCOM with the literal text ': IMS RC CODE NOT IN ACCEPTABLE LIST' delimited by SIZE and stores the result into CC-ERROR-MESSAGE of CCCOM
[Call Error Handler]
The system needs to handle the error condition → The system calls the error handler program 'CERR' using CCCOM as the parameter to process the error
[Status Code is Invalid]
The counter I exceeds 12 indicating all acceptable status codes have been checked without a match → The system constructs an error message by concatenating the status code with the text ': IMS RC CODE NOT IN ACCEPTABLE LIST' and stores it in CC-ERROR-MESSAGE OF CCCOM, then invokes the error handler program CERR with CCCOM as parameter, and returns control to the caller
[Build Error Message]
The status code is not found in the acceptable status table (CC-ACC-STATUS-TAB) after checking all 12 entries → The system builds an error message by concatenating the status code with the text ': IMS RC CODE NOT IN ACCEPTABLE LIST' and stores the complete message in CC-ERROR-MESSAGE of CCCOM
[Call Error Handler Program 'CERR']
The status code validation fails after checking all acceptable status codes → The system calls the error handler program 'CERR' passing CCCOM as parameter to process the error condition
[Move PCB Name to Error Message]
The system needs to report the error condition → The PCB mnemonic name is moved to the error message PCB name field
[Move PCB Number to Error Message]
The system continues building the error message → The PCB number is moved to the error message PCB number field
[Construct Error Message: 'ZERO PCB ADDR ERROR MESSAGE']
The system needs to format the complete error message → The standardized 'ZERO-PCB-ADDR-ERROR-MESSAGE' is constructed containing the PCB name and number
[Move Error Message to Common Area Error Field]
The system prepares to invoke error handling → The error message is moved to the CC-ERROR-MESSAGE field of the CCCOM common area
[Call Error Handler Program 'CERR' with Common Area]
The system needs to handle the unrecoverable error condition → The error handler program 'CERR' is called with the CCCOM common area containing the error details

As an EDI Gateway Service,
I want to orchestrate and execute all WRITMSGL EDI data mapping and validation logic,
So that I can ensure strict compliance with US Customs (P140) automated payload constraints in a single consolidated service.

Prerequisites & Setup

[Initialize Message Writing Functionality]
The system proceeds to extended message processing → The WRITMSGX program is called with all six parameters (P1, P2, P3, P4, P5, P6) to process the extended message operation

Core Acceptance Criteria

[1: Message Writing Initialization]
The system begins message processing workflow → The system invokes the WRITMSG module to initialize message writing operations
[2: Extended Message Writing]
The system proceeds to extended message processing → The system invokes the WRITMSGX module with all six parameters (P1, P2, P3, P4, P5, P6) to Execute extended message writing operations
[End Program]
All message processing steps are finished → The system terminates the program and returns control to the calling program
[Call WRITMSG Program]
The system begins the message processing workflow → The WRITMSG program is called to initialize message writing functionality without any parameters
[End: Message Writing Initialization]
All message writing operations are finished → The system returns control to the calling program
[Call WRITMSGX Program with 6 Parameters]
The extended message writing process is initiated → The system calls the WRITMSGX program with all six parameters (P1, P2, P3, P4, P5, P6) to generate the extended message output

Structural Validations

None explicitly identified in logic extraction.

As an EDI Gateway Service,
I want to orchestrate and execute all GCCCARFM EDI data mapping and validation logic,
So that I can ensure strict compliance with US Customs (P140) automated payload constraints in a single consolidated service.

Prerequisites & Setup

None explicitly identified in logic extraction.

Core Acceptance Criteria

[7:Count Numeric Digits]
Processing remaining characters → Consecutive numeric digits are counted until a space or end of input is encountered
[Alphabetic Character Found]
The character is alphabetic and prefix length is within limits → The character should be moved to the output prefix section and position counters incremented
[Skip Spaces After Prefix - Move past any spaces between alphabetic prefix and numeric portion]
The system encounters one or more space characters between the alphabetic prefix and numeric portion → The system advances the position counter past all consecutive spaces until it finds a non-space character or reaches the end of the input (position 20)

Structural Validations

[Check if prefix exceeds 4 characters?]
The prefix contains more than 4 alphabetic characters (WS-I2 > 4) → The system should validate the character immediately following the 4th alphabetic character
[Next Character is Numeric?]
The system examines the character immediately following the 4th alphabetic character → If the next character is numeric, the prefix is considered valid despite exceeding 4 characters
[Next Character is Space?]
The system examines if the next character is a space → If the next character is a space, the prefix is considered valid despite exceeding 4 characters

As an EDI Gateway Service,
I want to orchestrate and execute all GCCDBL EDI data mapping and validation logic,
So that I can ensure strict compliance with US Customs (P140) automated payload constraints in a single consolidated service.

Prerequisites & Setup

[Initialize Loop Counter to 1]
The system begins checking route segments → Loop counter is set to 1 and route found status is set to false

Core Acceptance Criteria

[Routing Found?]
Routing segment 13 information is not found → The double stack count is reset to zero
[14:Classify South-bound Traffic]
First carrier is CPRS AND second carrier is CSXT AND route includes DET → The traffic type is set to CSXT
[14:Classify South-bound Traffic]
First carrier is CPRS AND second carrier is NS AND route includes DET → The traffic type is set to NS
[15:Handle North-bound Traffic]
First carrier is CSXT or NS AND second carrier is CPRS AND route includes DET → The double stack count is reset to zero
[Set Waybill Number as Search Key]
The system prepares to search for waybill records in the database → The waybill number is set as the root key for the FWSWRWR segment search
[Read FWSWRWR Segment]
The system executes a database read operation on the FWSWRWR segment → The system attempts to locate and retrieve the corresponding waybill record
[Set Status: Waybill Found]
The database operation returns a valid waybill record → The system sets the internal status flag to indicate the waybill was found and is valid for further processing
[Set Status: Waybill Not Found]
The database operation does not return a valid waybill record → The system sets the internal status flag to indicate the waybill was not found in the database
[Exit - Invalid Waybill]
The system has determined the waybill does not exist → The system exits the double-stack counting process and returns control without performing any further waybill-related operations
[Read Route Segments]
The system attempts to retrieve route segment 13 information → Route segment data is accessed for detailed routing analysis
[Examine Route Pairs]
The system examines route information in sequential pairs up to 9 segments → Route pairs are analyzed for carrier sequence and destination patterns
[Set Segment Type to SHIPROOT]
The system prepares to query the shipment database → The segment type should be set to 'SHIPROOT' and the saved equipment key should be used as the root key for the query
[Call SHIPROOT Database]
The system executes the database call to retrieve shipment information → The FWCWBIO program should be called with the configured parameters to access the SHIPROOT database
[Proceed to Route Analysis]
The system processes the traffic type classification → Proceed to Execute detailed routing segment analysis to determine the specific traffic type
[Build Routing Segment Key]
The system needs to analyze routing segment information → The routing segment key is built using the US CCN key from the shipment routing record
[Set Record Type to '13']
Building the routing segment key → The record type is set to '13' to identify routing segment records
[Set Sequence to '0001']
Setting up the complete key structure → The sequence number is set to '0001' to identify the first routing segment
[Read Routing Segment SEG13]
The system attempts to read routing segment SEG13 data → The routing segment record is retrieved from the database using the constructed key
[Prepare for Route Segment Analysis]
The system confirms routing segment availability → The system prepares to analyze individual route segments within the routing data
[Reset Double-Stack Count to Zero]
The routing segment record is not found → The double-stack platform count is reset to zero
[Get Current and Next Route Segment]
The system needs to evaluate route segments → Current route segment and next route segment (counter + 1) are retrieved from routing information
[Extract Carrier Codes from Both Segments]
The system needs to analyze carrier routing → Move current segment to route-info-one and next segment to route-info-two for carrier code analysis
[CPRS to CSXT with DET Route?]
First carrier is CPRS and second carrier is CSXT and route includes DET → Set traffic type to CSXT and mark route as found
[CPRS to NS with DET Route?]
First carrier is CPRS and second carrier is NS and route includes DET → Set traffic type to NS and mark route as found
[CSXT/NS to CPRS with DET Route?]
First carrier is either CSXT or NS and second carrier is CPRS and route includes DET → Reset double-stack count to zero and mark route as found
[Increment Loop Counter]
No carrier routing conditions are met → Increment loop counter by 1 to check the next segment pair
[Calculate Next Segment Position]
The system needs to identify the next segment for paired analysis → The system increments the current position by 1 to get the next segment position
[Extract Carrier Code from First Segment]
The system processes the segment for carrier analysis → The system extracts the complete routing information from the first segment
[Extract Carrier Code from Second Segment]
The system processes the segment for carrier analysis → The system extracts the complete routing information from the second segment
[Store First Carrier Code]
The system needs to preserve the first carrier code for comparison → The system stores the first segment routing information in the first route info variable
[Store Second Carrier Code]
The system needs to preserve the second carrier code for comparison → The system stores the second segment routing information in the second route info variable
[CPRS to CSXT with DET Route?]
The first carrier is CPRS and the second carrier is CSXT and the route includes DET → Set the traffic type to CSXT and mark the route as found
[CPRS to NS with DET Route?]
The first carrier is CPRS and the second carrier is NS and the route includes DET → Set the traffic type to NS and mark the route as found
[CSXT/NS to CPRS with DET Route?]
The first carrier is either CSXT or NS and the second carrier is CPRS and the route includes DET → Reset the double-stack count to zero and mark the route as found
[More Segments to Check?]
The current segment pair has been processed and no route pattern has been found and there are more segments to evaluate → Continue to the next route segment pair for analysis
[CPRS to CSXT Route with DET?]
The first carrier is CPRS and the second carrier is CSXT and the route includes DET → Set the traffic type to CSXT and mark route as found
[CPRS to NS Route with DET?]
The first carrier is CPRS and the second carrier is NS and the route includes DET → Set the traffic type to NS and mark route as found
[CSXT/NS to CPRS Route with DET?]
The first carrier is CSXT or NS and the second carrier is CPRS and the route includes DET → Reset the double-stack count to zero and mark route as found
[More Segments to Check?]
The current segment counter is less than or equal to 9 and no route has been found yet → Continue processing the next route segment pair
[Extract First Route SCAC]
Processing route segment pairs for traffic classification → Extract the SCAC from the first route segment into route info one
[Extract Second Route SCAC]
Processing route segment pairs for traffic classification → Extract the SCAC from the second route segment into route info two
[Is First SCAC CSXT or NS?]
The first route SCAC is either CSXT or NS → Continue evaluating for potential north-bound traffic pattern
[Is Second SCAC CPRS?]
The second route SCAC is CPRS → Continue evaluating for Detroit interchange requirement

Structural Validations

[13:Evaluate Route Segments]
Current segment or next segment is empty or contains low values → The segment pair is skipped and processing continues with the next pair
[Waybill Record Found?]
If the result of the database operation → The system determines if the waybill record exists based on whether the database operation returned a valid record or not
[Route Segments Found?]
The system checks if route segment 13 was found → If route segments are not found, reset double-stack count to zero and terminate traffic type determination
[Examine Route Pairs]
Either current route segment or next route segment is empty or contains low-values → Skip to next iteration and stop processing remaining segments
[Routing Segment Found?]
The database read operation completes → The system determines whether the routing segment record was successfully found
[Both Segments Valid?]
Either current segment or next segment is empty or contains low-values → Set loop counter to 10 to exit the loop and stop processing
[Both Segments Have Valid Data?]
Either the current segment or the next segment contains spaces or low-values → The system terminates the route analysis and exits the segment checking process
[Are Both Segments Valid?]
Either the current route segment or the next route segment contains spaces or low-values → Skip processing this segment pair and terminate the route checking loop
[Valid Route Segments?]
Either the current route segment or the next route segment contains spaces or low-values → Skip processing and move to end of route classification
[Is Route Info Valid?]
Either the current route segment or the next route segment contains spaces or low-values → Skip this segment pair and exit the route checking process

As an EDI Gateway Service,
I want to orchestrate and execute all GCCSCAC EDI data mapping and validation logic,
So that I can ensure strict compliance with US Customs (P140) automated payload constraints in a single consolidated service.

Prerequisites & Setup

None explicitly identified in logic extraction.

Core Acceptance Criteria

[Load User Security Configuration]
The security record is successfully found and retrieved → The table segment data is moved to the user security segment structure
[Load User Security Data]
The lookup operation returns a successful status → The retrieved table segment data is moved to the user security segment structure

Structural Validations

None explicitly identified in logic extraction.

As an EDI Gateway Service,
I want to orchestrate and execute all GCCUTRIO EDI data mapping and validation logic,
So that I can ensure strict compliance with US Customs (P140) automated payload constraints in a single consolidated service.

Prerequisites & Setup

[Initialize Equipment Segments]
The system performs final cleanup of equipment-related data → All equipment segment data structures are initialized to clear any remaining equipment information
[Initialize Segment and Equipment Counters]
The system begins equipment segment processing → Segment quantity counter and equipment quantity counter are initialized to zero AND all empty car indicators are cleared
[Initialize Segment and Equipment Counters]
The system begins equipment calculation → Both segment quantity counter and equipment quantity counter are set to zero
[Initialize Indicator Set Counter Set to 1]
The system starts processing indicator sets → The indicator set counter is initialized to 1 to begin processing from the first set
[Initialize Indicator Set Counter = 1]
The system processes empty car indicators → The system loops through exactly 3 indicator sets, incrementing the counter from 1 until it exceeds 3

Core Acceptance Criteria

[2:Get Train Root Record Only]
Retrieving train information → The system fetches only the train root segment and populates the train header data
[3:Get Complete Train List]
Retrieving complete train information → The system first retrieves the train root segment, and if successful, proceeds to retrieve equipment segments
[5:Insert New Train with Equipment]
Creating a new train record → The system inserts the train root segment first, and if successful, proceeds to insert equipment segments
[10:Extract Empty Car Indicators]
Processing equipment information → The system extracts empty car indicators from each segment, validates numeric values, and maps them to the appropriate car positions
[11:Build Train Root Segment]
Building the root segment for database storage → The system moves train header data to the root segment structure, sets timestamps, and builds secondary indexes
[12:Process Equipment Segments for Insert]
Inserting equipment information → The system divides equipment into segments of 50 items each, fills remaining positions with spaces, and inserts each segment with sequential key numbers
[13:Pack Empty Car Indicators]
Storing equipment segment data → The system packs indicators into 3 sets of 18 indicators per segment, validates numeric values, and stores zero for non-numeric indicators
[Move Train Header Data to Output Structure]
The system processes the retrieval results → The complete train header segment data is moved to the output train list structure and the operation return code is set to indicate success
[Read First Equipment Segment]
The system reads the first equipment segment → Equipment data is retrieved from the equipment database if available
[Store Equipment Data in Train List]
The system processes the equipment data → Equipment information is stored in the corresponding train list segment position
[Extract Empty Car Indicators from Segment]
The system processes empty car indicators from the segment → Empty car indicator flags are extracted and prepared for unpacking
[Unpack Empty Car Indicator Flags]
The system unpacks the indicator flags across 3 indicator sets with 18 positions each → Individual car empty status flags are stored in the train list for cars 1 through 50 of the current segment
[Read Next Equipment Segment]
The system attempts to read the next equipment segment → Next equipment segment data is retrieved if available
[Calculate Total Equipment Count]
The system calculates the total equipment count → Total equipment count is computed as (number of complete segments × 50) plus remaining equipment in partial segment
[Clear Unused Segment Areas]
The system processes unused segment areas → All unused equipment positions and empty car indicators beyond the actual count are cleared to spaces and low-values respectively
[Calculate Starting Car Position and Calculate Last Car Position]
The system needs to determine the car position range for that segment → The starting car position is calculated as 50 times (segment index minus 1) and the last car position is calculated as starting position plus 50
[Indicator Set <= 3?]
The system processes empty car indicators for the segment → The system iterates through exactly 3 indicator sets, processing each set sequentially
[Indicator <= 18 AND Car < Last Car Position?]
The system processes individual indicators within the set → The system processes indicators while the indicator counter is 18 or less AND the current car position is less than the last car position for the segment
[Increment Car Position and Map Indicator Value to Car Position]
Each indicator is mapped to a car position → The car position is incremented by 1 for each indicator processed, and the indicator value is assigned to the corresponding car position
[Equipment Count Valid 1-2500 Range]
The equipment quantity is between 1 and 2500 inclusive → Proceed with inserting the train root record followed by inserting the equipment data if root insert is successful
[Equipment Count Valid 1-2500 Range]
The equipment quantity is between 1 and 2500 inclusive → Delete the existing train record, then insert new train root record followed by inserting the equipment data if both delete and root insert are successful
[Build Train Root Segment]
The equipment quantity validation passes → The system copies the train header data to the root segment structure
[Set Creation Timestamp]
The train root segment is built → The system sets creation timestamp with current date, time, terminal, user ID, and module name
[Insert Train Header to Database]
The insert operation is executed → The system calls the database insert function to store the train header record
[Calculate Equipment Segments Needed]
Processing equipment for storage → The system divides the equipment quantity by 50 to get the number of full segments and calculates remainder for partial segment
[Divide Equipment into 50-item Segments]
There is a remainder from the division by 50 → The system adds 1 to the segment count, fills remaining positions in the partial segment with spaces, and prepares each segment with up to 50 equipment items
[Process Each Equipment Segment]
Processing each segment sequentially → The system copies the segment data to the equipment structure and sets the segment key number
[Pack Empty Car Indicators]
Empty car indicators need to be stored → The system calculates car positions based on segment index, processes 3 sets of 18 indicators each, validates numeric indicators and defaults non-numeric to 0, and packs the indicators into the equipment segment structure
[Insert Equipment Segment to Database]
The segment is ready for storage → The system calls the database insert function to store the equipment segment
[Divide Total Equipment Count by 50]
The system needs to determine how many full segments are required for storage → The system divides the total equipment count by 50 to get the number of full segments and calculates any remainder equipment
[Add 1 to Segment Count for Partial Segment]
The remainder equipment count is greater than zero → The system adds 1 to the total segment count to accommodate the partial segment and calculates the starting position for padding empty spaces
[Pad Remaining Positions with Spaces]
The system processes equipment positions from the remainder position plus 1 through position 50 → The system fills each unused position with spaces to complete the segment structure
[Insert Equipment Segments]
Inserting equipment segments → Divide equipment into segments of 50 items, insert each segment with sequential numbering, and handle partial segments appropriately
[Pack Empty Car Indicators]
Processing empty car indicators → Extract and pack empty car indicator data from the equipment segments into the appropriate storage format
[Read First Equipment Segment from GCSUTDP]
The system performs the first equipment segment read operation → The system reads the next equipment segment from GCSUTDP database
[Store Equipment Data in Segment Array]
The system processes the segment data → Equipment data is moved to the segment array at current segment index AND empty car indicators are extracted and stored for the current segment
[Read Next Equipment Segment]
The system needs to read the next equipment segment → The system performs next equipment segment read operation from GCSUTDP
[Calculate Final Segment Count]
The system finalizes equipment counting → Final segment count is calculated by subtracting 1 from current segment index AND equipment count in last segment is determined by counting non-space equipment entries up to position 50
[Clear Remaining Segment Slots]
The system needs to clean up unused segment slots → All segment slots from current segment index to 50 are cleared to spaces AND corresponding empty car indicators are set to low-values
[Calculate Total Equipment Count]
The system calculates total equipment → Total equipment count equals (segment count multiplied by 50) plus equipment count in last segment
[Set Equipment Count in Train List]
The system finalizes equipment processing → Total equipment count is moved to the train list equipment quantity field
[Read Equipment Segments from Database]
The system needs to retrieve equipment segments → The system performs a database read operation to get the next equipment segment
[Process Current Segment]
The segment data is available for processing → The system moves the equipment data to the working segment area and processes empty car indicators for the segment
[Count Equipment in Last Segment]
The system needs to determine the exact equipment count → The system iterates through positions 1 to 50 in the final segment and counts non-empty equipment positions
[Calculate Total Equipment Count]
The system needs to determine total equipment count → The system multiplies complete segments by 50 and adds the equipment count from the final segment
[Clear Unused Segment Areas]
The system needs to clean up unused storage areas → The system initializes unused segment areas to spaces and sets empty car indicators to low values
[Calculate Starting Car Position Based on Segment Index, Calculate Starting Car Position, Calculate Car Position Range]
The system needs to determine the car position range for that segment → The starting car position is calculated as 50 times (segment index minus 1) and the ending car position is calculated as starting position plus 50
[Calculate Starting Car Position]
The system needs to determine the car position range for the segment → The starting car position is calculated as 50 times (segment index minus 1) and the ending car position is calculated as starting position plus 50
[Copy Train Header Data to Root Segment]
The system needs to build a train root segment → The train header data is copied to the root segment structure (GCUTR-TRAIN-ROOT-SEGMENT)
[Calculate Number of Segments Needed]
The system calculates storage requirements → The equipment quantity is divided by 50 to determine the number of full segments needed, with any remainder indicating additional equipment requiring one more segment
[Add One More Segment]
The remainder of equipment items is greater than zero → One additional segment is allocated to accommodate the remaining equipment items
[Fill Remaining Positions with Spaces]
There are unused positions in the segment after placing all remaining equipment → All unused positions from the next available position through position 50 are filled with spaces
[More Segments to Process?]
The system processes segments sequentially starting from segment 1 → Each segment is processed in order until the segment counter exceeds the total number of segments required
[Move Equipment Data to Current Segment]
The segment is being prepared for insertion into the database → The equipment data from the working segment is moved to the database segment structure
[Set Segment Number]
The segment requires a unique identifier → The current segment index is assigned as the segment key number
[Pack Empty Car Indicators for Segment]
The segment is being prepared for database insertion → The empty car indicators are packed from the expanded 150-position format into the compressed 3-group format for the segment
[Insert Equipment Segment to Database]
The segment is ready for permanent storage → The segment data is inserted into the GCSUTDP database table
[Divide Total Equipment Count by 50]
The system processes equipment for storage in segments → The total equipment count is divided by 50 to determine complete segments and any remainder equipment count
[Add 1 to Segment Count for Partial Segment]
The remainder count is greater than zero → One additional segment is added to the total segment count and the remainder position is incremented by 1
[Fill Remaining Positions with Spaces]
Equipment positions from the remainder position to position 50 need to be processed → All unused equipment positions in the segment are filled with spaces
[Move Equipment Data to Segment Structure]
Each segment is being prepared for insertion → The equipment data from the train list segment is moved to the database equipment structure
[Set Segment Number]
The segment data structure is being prepared → The current segment index is assigned as the segment key number
[Pack Empty Car Indicators for Segment]
The segment is being prepared for database storage → Empty car indicators are packed from the train list format into the database segment format across multiple indicator sets
[Insert Equipment Segment to Database]
The segment is ready for database storage → The equipment segment is inserted into the database using the equipment insertion process
[Individual Indicator <= 18 AND Car < Last Car?]
The system processes individual indicators within the set → The system continues processing while the individual indicator counter is 18 or less AND the current car position is less than the last car position for the segment
[Move Compressed Indicators to Database Segment]
All indicators in the current set are processed → The compressed indicator values are moved from working storage to the corresponding database segment field
[Process Next Indicator Set?]
The system begins indicator processing → The system processes exactly 3 indicator sets, iterating from set 1 to set 3
[Save Indicator Set to Database]
The indicator set processing is complete → The complete indicator set from working storage is moved to the database segment structure
[Move New Header Data to Train Record]
The system prepares to update the train record → The new train header data is moved from the input structure to the train root segment

Structural Validations

[9:Retrieve Equipment Segments]
Retrieving equipment information → The system reads equipment segments sequentially until end of data or maximum of 50 segments is reached, setting too-many-equipment flag if limit exceeded
[Equipment Segment Found?]
The system checks if equipment segment data was found → Processing continues with equipment data storage if found, otherwise proceeds to calculate totals
[More Segments Available?]
The system checks for more available segments → Processing continues if under 50 segments and more data exists, stops if no more data, or returns error if 50 segment limit reached
[Is Indicator Set Numeric?]
The system checks the indicator set format → If the indicator set is numeric, use the actual value; otherwise set the indicator set to zero
[Header Creation Successful?]
The header creation operation completes → If successful, proceed to insert equipment segments; if failed, terminate the replace operation
[More Segments Available AND Segment Count < 50?]
The system checks whether to continue reading more segments → Loop continues IF segment was found successfully AND segment index is less than 50, OTHERWISE loop terminates
[Set Too Many Equipment Status]
The system found more segments available after reading 50 segments → System sets too many equipment status flag to true
[Reached Maximum 50 Segments?]
The segment index reaches 50 → The system stops processing additional segments to enforce the maximum limit
[Total > Maximum Limit?]
Additional equipment segments are found beyond the 50 segment limit → The system sets the too many equipment flag to indicate equipment exceeds maximum allowed
[Check if Database Indicator is Numeric]
The system needs to process this indicator value → The system checks if the indicator value is numeric before using it
[Indicator <= 18 AND Car < Last Car?]
If whether to continue processing the next indicator → Processing continues only if the indicator counter is 18 or less AND the current car position is less than the last car position for the segment
[Car Position Within Range?]
The system checks if the car position is valid → The car position must be less than the last car position for the segment range

As an EDI Gateway Service,
I want to orchestrate and execute all GCSTONLY EDI data mapping and validation logic,
So that I can ensure strict compliance with US Customs (P140) automated payload constraints in a single consolidated service.

Prerequisites & Setup

[Initialize Call Letters Processing]
Call letters processing initialization begins → Call letters buffer is cleared to spaces and processing counter J is set to 1
[Initialize Output Record Structure]
Output record initialization begins → Output record is cleared to spaces and call letters buffer is moved to the first position of the data segment OLV record

Core Acceptance Criteria

[2:Function Code Processing - Is CC-USER-FUNC-CODE = 'WRAP'?]
The user function code equals 'WRAP' → The system performs final segment processing, sets first record flag to 'Y', and terminates processing
[4:Terminal Information Setup]
Terminal information is needed for message routing → The system calls FROMBASE to retrieve terminal information using IO-PCB with parameter value 8
[6:Message Header Preparation]
Transaction code and input record are available → The system moves transaction code to control segment origin transaction field, moves input record to control segment menu header, and sets flag byte to low-values for GCT026 transactions or OLV indicator for other transactions
[11:Input Record Storage]
Input record needs to be stored in data segment → The system sets record counter to 2 and moves input record to data segment position 2
[13:Record Counter Management]
The record counter needs to be updated → The system increments the record counter by 1 and moves the input record to the corresponding data segment position
[14:Batch Size Check - Is I = 22?]
The record counter equals 22 → The system sets segment length to 1786 and initiates data segment transmission, otherwise it continues accepting more records
[15:Data Segment Transmission]
The system is running in TPE environment → The system calls CIMS with ISRT operation using MST-PCB and data segment, otherwise it uses KX2BMP method for transmission
[16:Record Reset]
The batch of 22 records has been processed → The system resets the record counter to 0 to start a new batch
[18:Dynamic Segment Length Calculation]
The record counter != 0 → The system calculates segment length as record counter multiplied by 81 plus 4 bytes overhead
[6:Message Header Preparation]
The system is running in TPE environment → The system calls CIMS with CHNG operation for setup and PURG operation for control segment processing, otherwise it uses KX2BMP method with appropriate parameters
[Check if user function code is 'WRAP' to determine processing path]
The system checks if CC-USER-FUNC-CODE equals 'WRAP' → If the function code is 'WRAP', execute final segment processing and exit; otherwise continue to normal record processing
[Execute Final Segment Processing]
The system needs to finalize processing → Execute the final segment processing routine (30-SEND-LAST-SEG)
[Prepare Message Header]
Message header preparation begins → The transaction code is copied to the control segment origin transaction field and the input record is copied to the control segment menu header field
[Set Low Values in Flag Byte]
The transaction code equals 'GCT026' → The flag byte in the control segment is set to low values
[Set OLV Indicator in Flag Byte]
The transaction code != 'GCT026' → The flag byte in the control segment is set to OLV indicator value
[Send Control Segment to Queue]
Control segment transmission is initiated → The control segment is sent to the processing queue using the appropriate method for the current runtime environment
[Store Input Record in Second Position]
Input record storage begins → The input record is moved to the second position of the data segment OLV record and counter I is set to 2
[Move Transaction Code to Control Segment]
The system processes the transaction → The transaction code from the communication control block is moved to the original transaction field of the control segment
[Move Input Record to Menu Header]
The control segment is being prepared → The input record is moved to the menu header field of the control segment
[Set Flag Byte to LOW-VALUES]
The transaction code is 'GCT026' → The flag byte of the control segment is set to low values
[Set Flag Byte to OLV-IND]
The transaction code is not 'GCT026' → The flag byte of the control segment is set to OLV indicator
[Send Control Segment via CIMS]
The control segment needs to be transmitted → The system calls CIMS with purge operation to send the control segment
[Prepare KX2BMP Parameters]
The control segment needs to be transmitted → The system initializes timestamp fields to low values, calculates segment length, and moves the control segment to KX2BMP area
[Send Control Segment via KX2BMP]
The control segment transmission is initiated → The system performs KX2BMP insert operation to send the control segment
[Set Flag Bits to 64]
System prepares to send control segment → Flag bits are set to 64 and accept status is cleared to spaces
[Move Transaction Code to Control Segment]
Control segment is being prepared → Transaction code is moved to original transaction field and input record is moved to menu header field of control segment
[Is Transaction Code = 'GCT026'?]
Transaction code is not 'GCT026' → Flag byte of control segment is set to OLV indicator
[Send Control Segment via CIMS]
Control segment needs to be sent → CIMS program is called with PURG operation using CCCOM, MST-PCB, and CONTROL-SEG parameters
[Send Control Segment via KX2BMP]
Control segment needs to be sent → Timestamp and task number are set to low values, control segment length is calculated, control segment is moved to KX2BMP area, and KX2BMP-INSERT is performed
[Move Transaction Code to Control Segment Header]
The system prepares the message header → The transaction code is moved to the original transaction field of the control segment
[Move Input Record to Control Segment Menu Header]
The system prepares the message header → The input record is moved to the menu header field of the control segment
[Set Flag Byte to Low Values for GCT026]
The system configures the control segment flag byte → The flag byte is set to low values to indicate GCT026-specific processing
[Set Flag Byte to OLV Indicator for Other Transactions]
The system configures the control segment flag byte → The flag byte is set to the OLV indicator value for standard processing
[Move Call Letters Data to First Output Record Position]
The system needs to populate the first output record position → The formatted call letters data should be moved to the first position of the output data segment
[Replace First Space with '#' Character]
The system processes the call letters record in OLV-REC OF DATA-SEG (1) → The first space character in the call letters record is replaced with '#' character
[Set Position to 2]
The system needs to store the input record in the data segment → The position counter I is set to 2 to place the input record in the second position of the output data array
[Store Input Record in Output Data Segment]
The system processes the input record → The input record is moved to the data segment at the position indicated by the record counter
[Set Data Segment Length to 1786]
The system prepares the data segment for transmission → The data segment length is set to 1786 bytes
[Send Data Segment to Message Queue]
The system sends the data segment → If running in TPE environment, use CIMS with ISRT operation, otherwise use KX2BMP insert operation
[Increment Record Counter - ADD 1 TO I]
The system processes a subsequent record after the first record → The record counter I is incremented by 1 to point to the next available position
[Store Input Record in Data Segment at Position I]
The system needs to store the input record in the data segment → The input record is moved to the OLV-REC position I within the data segment array
[Is Record Count = 22?]
If the current record count → If the record count equals 22, batch processing is triggered; otherwise, processing continues to exit
[Set Segment Length to 1786]
The system prepares to send the data segment → The segment length of the data segment is set to 1786
[Send Data Segment]
The system processes the full batch → The data segment is sent using the appropriate method based on the runtime environment (CIMS for TPE or KX2BMP for BPE)
[Set Data Segment Length to 1786]
The batch size limit is reached → The data segment length is set to 1786 bytes
[Clear Accept Status]
The transmission process begins → The accept status field is cleared to spaces
[Check Environment Type]
The system checks the runtime environment → If running in TPE environment, use CIMS transmission method, otherwise use KX2BMP transmission method
[Send via CIMS - TPE Environment]
Data transmission is initiated → The system calls CIMS service with ISRT operation to insert the data segment
[Calculate KX2BMP Length]
Preparing for KX2BMP transmission → The KX2BMP length is computed as the length of the data segment
[Move Data to KX2BMP Area]
Preparing data for KX2BMP transmission → The data segment is moved to the KX2BMP area
[Execute KX2BMP Insert]
Data transmission is executed → The KX2BMP-INSERT procedure is performed to transmit the data
[Reset Record Counter to 0]
The transmission is complete → The record counter I is reset to 0
[Clear Output Records]
Preparing for the next batch of records → The output record area is cleared to spaces
[Call CIMS with Message Parameters]
A message transmission operation is requested → The system calls CIMS program with the appropriate message parameters and control blocks
[Set KX2BMP Parameters]
Message transmission is initiated → The system sets timestamp fields to low-value, sets task number to low-value, and configures the destination parameter
[Calculate Message Length]
The message length needs to be determined → The system computes the KX2BMP length as the length of the message segment
[Move Message to KX2BMP Area]
The message content needs to be prepared for transmission → The system moves the message segment content to the KX2BMP area
[Call KX2BMP Program]
The KX2BMP transmission is executed → The system calls KX2BMP program with all required parameters including program name, destination, application ID, system ID, operation, length, area, return code, timestamp, task number, and timestamp2
[Check Environment Type]
The system checks the environment parameter from system environment → If environment parameter is empty or low-value, set environment type to TPE, otherwise set environment type to BPE
[Set CCCOM Control Block]
CIMS call preparation is initiated → Set up CCCOM control block with communication parameters and clear accept status
[Set Operation Type]
Operation type needs to be determined → Select CHNG for initial setup, PURG for control segment processing, or ISRT for data segment processing
[Set Data Segment]
Data segment needs to be assigned → For CHNG operations use MST-BMP, for PURG operations use CONTROL-SEG, for ISRT operations use DATA-SEG
[Execute CIMS Call]
CIMS operation execution is required → Call external CIMS program with CCCOM control block, operation type, PCB reference, and data segment
[Clear Timestamp Fields]
KX2BMP parameters are being set up for message processing → Both primary and secondary timestamp fields are cleared to low values
[Clear Task Number]
KX2BMP parameters are being set up for message processing → The task number field is cleared to low value
[Calculate Message Length]
KX2BMP parameters are being set up and message length needs to be determined → The message length is calculated based on the length of the control segment or data segment being transmitted
[Move Data to KX2BMP Area]
KX2BMP parameters are being finalized for transmission → The control segment or data segment content is moved to the KX2BMP transmission area
[Reset Record Counter to 0]
The batch transmission is complete → The record counter should be reset to 0 to start accumulating the next batch
[Clear Output Records with Spaces]
The system needs to prepare for the next batch → The output record area should be cleared with spaces
[Are there remaining records to send? Check if record counter > 0]
The system checks the record counter to determine if records exist → If record counter is greater than 0, proceed to calculate segment length and send records; otherwise skip to final purge message
[Calculate Dynamic Segment Length - Length = Number of Records × 81 + 4]
The system needs to determine the segment length for the final data transmission → Calculate segment length as number of records multiplied by 81 plus 4 bytes overhead
[Send Data Segment with Remaining Records to Message Queue]
The system is ready to send the final data segment → Send the data segment with calculated length to the message processing system based on runtime environment (TPE or BPE)
[Send Final Purge Message to Complete Transaction]
The system needs to complete the WRAP function processing → Send a purge message to the message processing system if running in TPE environment to finalize the transaction
[Calculate Variable Length: Records × 81 + 4]
The system needs to send the last segment with partial data → Calculate segment length as number of records multiplied by 81 plus 4 bytes overhead and apply this length to the data segment
[Set Fixed Length: 1786 bytes]
The record counter reaches 22 → Set the data segment length to the fixed value of 1786 bytes
[Are there remaining records to process?]
Determining how to calculate segment length → If record counter I is not equal to 0, use variable length calculation; otherwise use fixed length for complete batches
[Check Environment Type]
The environment type is determined as either TPE or BPE → TPE environment uses CIMS service while BPE environment uses KX2BMP service
[Use CIMS for TPE Environment]
A message queue operation is required → The system calls CIMS service with appropriate parameters for the operation type
[Set KX2BMP Parameters]
KX2BMP service is selected for message processing → System sets timestamp fields to low-value, sets task number to low-value, and configures destination from MST-BMP
[Calculate Message Length]
The data segment length needs to be determined → System computes KX2BMP-LENGTH as the length of the data segment being sent
[Move Data to KX2BMP Area]
Data needs to be moved to KX2BMP service area → System moves the data segment to KX2BMP-AREA for service processing
[Set Message Timestamp to Low-Value]
The system sets up message parameters → The primary timestamp and secondary timestamp are both set to low-value and the task number is set to low-value
[Calculate Message Length]
The system prepares the message parameters → The message length is calculated based on the length of the data segment or control segment being processed
[Move Data to Message Area]
The system prepares the message for service call → The data segment or control segment is moved to the message area
[Execute KX2BMP Service Call]
The system needs to send business data through external service → The KX2BMP service is called with all required parameters including program name, destination, application ID, system ID, operation type, message length, data area, return code, timestamps, and task number
[Set Message Parameters]
The system is running in BPE environment and preparing message parameters → The timestamp, timestamp2, and task number fields are cleared to low values
[Calculate Message Length]
The system needs to determine the message size → The message length is computed based on the actual data segment or control segment length
[Move Data to Message Area]
The system is ready to send the message → The data is moved to the message area for transmission
[Call KX2BMP Service]
The system needs to send data to external service → KX2BMP service is called with all required parameters including program name, destination, application ID, system ID, operation type, length, data area, return code, timestamp, task number, and timestamp2
[Execute KX2BMP Call]
KX2BMP service is called with program parameters including destination, operation, length, and data area → External KX2BMP service processes the request and returns a status code
[Terminate Processing]
System has logged errors and set appropriate return codes → System terminates all processing immediately without continuing to next steps

Structural Validations

[10:Special Character Replacement]
The call letters contain space characters → The system replaces the first space character with '#' symbol in the data segment record
[Replace First Space with '#']
Space replacement processing occurs → The first space character in the data segment OLV record at position 1 is replaced with '#'
[KX2BMP Return Code OK?]
The KX2BMP return code is evaluated → The system determines transmission success if the return code indicates OK status
[Display Error Messages]
The transmission failure is detected → The system displays error messages with the return code, sets return code to 99, calls error handling functions, and stops program execution
[Display Error Messages]
Error handling is triggered → System displays error messages with return code, sets return code to 99, calls error handling functions, and stops program execution
[Display Error Messages]
The return code indicates an error condition → Error messages are displayed, return code is set to 99, condition code is set, and processing is stopped
[Display Error Messages]
The return code indicates an error condition → Error messages are displayed showing the failure and the specific return code received
[Log Error Messages]
System needs to record the failure for troubleshooting purposes → System displays error boundary markers and the specific return code to system error output

As an EDI Gateway Service,
I want to orchestrate and execute all GCX904 EDI data mapping and validation logic,
So that I can ensure strict compliance with US Customs (P140) automated payload constraints in a single consolidated service.

Prerequisites & Setup

[Initialize Report Line Counter]
The system begins processing report message lines → The mail subscription counter is initialized to 1 to track the current position in the message line array
[File Opening Successful?]
The file opening status is not successful (not equal to '00') → An error message is displayed to indicate the file opening failure

Core Acceptance Criteria

[4:Process Report Data Lines]
The line is identified as a message line AND the PDF length equals 132 → The system skips processing this line and continues to the next line, otherwise processes the line normally
[5:Filter Message Lines]
Processing the message line for JCL output → The system increments sequence number, splits the 132-character line into two 66-character segments, assigns sequence numbers (positions 1-4) and group numbers (positions 71-72) to each segment, and increments group number by 50 for each segment
[Set Message Class Parameters]
Setting up message class parameters → The system moves the appropriate job configuration flag to the spool user ID field
[Is Message Line AND PDF Length = 132?]
If whether to process the line → The line should be skipped and processing should continue to the next line without creating JCL segments
[Assign Sequence Number and Group Number]
The system creates a line segment → A sequence number should be incremented and assigned to positions 1-4 of the JCL line, and a group number should be assigned to positions 71-72
[Create First Segment: Characters 1-66]
The system processes the first segment → Characters 1-66 from the message line should be moved to positions 5-70 of the JCL line
[Create Second Segment: Characters 67-132]
The system processes the second segment → Characters 67-132 from the message line should be moved to positions 5-70 of the next JCL line
[Assign Sequence Number and Group Number]
The system completes processing of each segment → The group number should be incremented by 50 to prepare for the next segment
[Store First Segment and Store Second Segment]
The system completes storing the segment → The line counter should be incremented by 1 to point to the next available JCL array position
[Is Message Line AND PDF Length = 132?]
The PDF length is set to 132 characters → Skip processing this line and continue to the next report line without creating any segments
[Create First Segment - Characters 1-66]
The line is ready for segment creation → Create the first segment using characters 1 through 66 of the original report line
[Create Second Segment - Characters 67-132]
Processing continues for the same report line → Create the second segment using characters 67 through 132 of the original report line
[Assign Sequence Number and Group Number]
The segment is ready for numbering → Increment the sequence number by 1 and assign it to positions 1-4 of the JCL line, and assign the current group number to positions 71-72
[Assign Same Sequence Number and Updated Group Number]
Processing continues to the next segment or operation → Increase the group number by 50 for subsequent use
[Increment Sequence Number]
The system begins creating a new segment from the report line → The sequence number must be incremented by 1 to ensure unique identification of each JCL line
[Move Sequence Number to Position 1-4]
The system constructs the JCL line structure → The sequence number must be moved to character positions 1-4 of the JCL line
[Extract Characters 1-66 from Report Line]
The system creates the first segment of the report line → Characters 1 through 66 from the original message line must be extracted for the first segment
[Move First 66 Characters to Position 5-66]
The system constructs the JCL line with the first segment content → The 66 characters must be moved to positions 5-66 of the JCL line, immediately following the sequence number
[Add Group Number to Position 71-72]
The system completes the JCL line structure for a segment → The current group number must be moved to positions 71-72 of the JCL line
[Increment Group Number by 50]
The system completes processing of the current segment → The group number must be incremented by 50 to prepare for the next segment
[Move to Next JCL Line]
The system finishes processing the current segment → The line pointer must be incremented by 1 to position for the next JCL line in the output array
[Add 50 to Group Number]
The system begins creating the second segment of the report line → The group number is increased by 50 from its current value
[Move Sequence Number to Position 1-4]
The system formats the second segment structure → The current sequence number is placed in character positions 1 through 4 of the output line
[Extract Characters 67-132 from Report Line]
The system creates the second segment → Characters 67 through 132 from the original report line are extracted for processing
[Move Characters 67-132 to Position 5-66]
The system formats the second segment output line → The extracted 66 characters are placed in positions 5 through 66 of the output line
[Move Group Number to Position 71-72]
The system completes the second segment structure → The group number is placed in character positions 71 through 72 of the output line
[Add 50 to Group Number for Next Processing]
The system prepares for processing the next report line → The group number is increased by an additional 50 to maintain sequential numbering
[Increment Line Counter]
The system completes the second segment creation → The output line counter is incremented by 1 to point to the next available output position
[Is Line a Message Line?]
The system moves the report line to the message line field and evaluates if it is a message line → The system identifies whether the line qualifies as a message line for further processing
[Is PDF Length = 132?]
The PDF length is set to 132 characters → The system skips the message line and continues to the next line without further processing
[Process Line - Split into Two 66-Character Segments]
The line needs to be processed for JCL output → The system splits the line into two 66-character segments, assigns sequence numbers, adds group numbers, and increments the group number by 50 for each segment
[Check Line Content Type]
If the line content to determine if it contains message data → The system identifies the line as either a message line or non-message line for further processing decisions
[Is Message Line?]
The system processes the report content → The system skips the message line and continues to the next report line without adding it to the JCL output
[Process Line Normally]
The system processes the report content → The system processes the line normally by adding sequence numbers, splitting into segments, adding group numbers, and including it in the JCL output
[More Report Lines to Process?]
The system checks if more lines need processing → Processing continues if the current line counter is less than the total number of lines AND the counter is 1981 or less, otherwise processing stops
[Get Next Report Line]
The system needs to process the next message line → The message line at the current counter position is moved to the working storage message line field
[Is Message Line AND PDF Length = 132?]
The line is identified as a message line type AND the PDF length is set to 132 characters → The line is skipped and processing continues with the next line without any JCL generation
[Increment Sequence Number]
The line is not skipped due to format restrictions → The sequence number counter is incremented by 1 to provide unique identification for the line segment
[Create First 66-Character Segment]
The first segment is being created → Characters 1 through 66 of the message line are extracted and prepared for JCL formatting
[Add Sequence Number and Group Number]
The JCL line is being formatted → The sequence number is placed in positions 1-4, the message segment in positions 5-70, and the group number in positions 71-72 of the JCL line
[Write First Segment to JCL Array]
The line needs to be stored for output → The formatted line is moved to the current position in the JCL output array
[Create Second 66-Character Segment]
The second segment is being created → Characters 67 through 132 of the message line are extracted and prepared for JCL formatting
[Add Sequence Number and Updated Group Number]
The second JCL line is being formatted → The incremented sequence number is placed in positions 1-4, the second message segment in positions 5-70, and the updated group number in positions 71-72 of the JCL line
[Write Second Segment to JCL Array]
The line needs to be stored for output → The formatted line is moved to the next position in the JCL output array
[Update Group Number Counter]
The group numbering needs to be updated for the next message line → The group number counter is increased by 50 to maintain proper grouping sequence
[Close Spool File]
The system initiates the file closure process → The system closes the spool file and displays an error message if the closure operation fails
[Display Completion Message]
The system completes the spool closure process → The system displays a message containing current date, time, process identifier, job file name, and script name to system error output

Structural Validations

[Check if File Exists]
The operation type is 'WRITE' → The system checks if the target spool file exists before proceeding with write operation
[Check if File Exists for Closing]
The operation type is 'CLOSE' → The system checks if the spool file exists before proceeding with close and job submission operations
[Check if File Exists for Closing]
The operation type is 'CLOSE' → Check if the target file exists before proceeding with closure and submission

As an EDI Gateway Service,
I want to orchestrate and execute all GCX003 EDI data mapping and validation logic,
So that I can ensure strict compliance with US Customs (P140) automated payload constraints in a single consolidated service.

Prerequisites & Setup

[Initialize Empty Security Segment]
The system initializes user permission data → The user security segment is set to spaces
[Initialize Equipment Processing Flags]
The system begins processing equipment → All processing state flags are set to their initial values: TR bond not found, TR not created for IT, TE bond not found, TE not created for TE, special location codes not found, US-MX export not found, and segment indicators reset
[Initialize SHIPCOMM to Spaces]
System needs to continue processing without shipment comments data → Initialize SHIPCOMM structure to spaces to ensure clean data state for subsequent processing
[Initialize User Authorization Flags]
The system processes the user security information → The system copies the user security segment data to working storage for authorization processing
[Initialize FEN and KCM Flags as Not Found]
The system begins Mexico customs documentation validation → Set FEN documentation flag to not found and KCM documentation flag to not found
[Initialize Email Parameters]
The system prepares email parameters → FROM usercode is set to default Merlin ID, TO usercode is set to default Merlin ID, subject line is cleared, message content is cleared, and item width is set to 080
[Initialize Email Parameters]
The email transmission process is initiated → The system shall set the sender as OM01247, clear recipient and copy fields, set item width to 080 characters, and initialize return status flags
[Initialize GCX141 Message Parameters]
The system prepares the export report message → All GCX141 input parameters are cleared and reset to initial state
[Initialize Continuation Email]
The system initializes a continuation email → Email message is cleared, line counter is reset, continuation message is added, and detail headers are re-added
[Initialize Segment Retrieval Parameters]
The system begins segment data processing → The system sets accept status to 'GE', clears working storage areas, enables underscore processing, sets function to Get Unqualified, disables index usage, and enables retrieval of segments 07, 02, and 08
[B250-RETRIEVE-SEG07: Initialize Segment Retrieval]
The system begins segment data retrieval → The system should initialize cargo segment retrieval parameters and set function to Get Unique operation
[Initialize Train Header Information]
The system begins the train list storage process → The train header information is initialized and cleared of any previous data to prepare for new train data storage
[Initialize Train Header Information]
The system begins train list storage process → The train header information structure is initialized to empty values
[Initialize GCX141 Message Parameters]
The system begins the report generation process → All GCX141 input parameters are initialized to blank values
[Initialize Car Waybill Parameters]
The system initializes waybill retrieval parameters → Set car type to all except 98-99, status to all status types, exclude EDI incomplete records, include temporary waybills, exclude corrector waybills, return lead waybill, and use latest waybill date
[Initialize Inquiry System Parameters]
The system needs to query the inquiry database for missing equipment details → Initialize inquiry system parameters and clear all status codes and segment data
[Initialize Log Message Structure]
The system initializes the log message structure → The GCX105-INPUT structure is cleared and ready for data population

Core Acceptance Criteria

[2:User Security Validation]
The user's UTF authorization is not 'U' or 'S' AND the request is not an AEI train send request → Generate error message 13 (insufficient authorization) and set user access flag to NO
[9:Car Waybill Retrieval]
Car waybill lookup is performed → Retrieve latest waybill excluding temporary, corrector, and incomplete EDI waybills, and if car is loaded empty, treat as waybill not found
[11:Cargo Attachment to Train]
Cargo is immediate transport:
already created for IT
US-Canada-US with release status
default with release status
empty equipment
special manifest at Woburn PQ station
export at non-Laredo stations
→ Skip cargo attachment to train
[22:TE Bond Port Change Processing]
Request action is REPORT → Generate message 19 with station code, when request action is SEND and user is authorized for special manifest, generate message 20 and spawn port change manifest, when user is not authorized, generate message 43
[23:TR Bond Diversion Processing]
Request action is REPORT → Generate message 18, when request action is SEND and user is authorized for special manifest, generate message 23 and spawn detour manifest, when user is not authorized, generate message 43
[24:Border Clearance Detour Processing]
Cargo has release status and request action is REPORT → Generate message 18, when request action is SEND and user is authorized for special manifest, generate message 23 and spawn detour manifest, when user is not authorized, generate message 43, when cargo does not have release status, generate message 31
[25:US-US Movement Detour Processing]
Request action is REPORT → Generate message 18, when request action is SEND and user is authorized for special manifest, generate message 23 and spawn US-US detour manifest, when user is not authorized, generate message 43
[26:US-Mexico Export Detour Processing]
Request action is REPORT → Generate message 50, when request action is SEND and user is authorized for special manifest, generate message 23 and spawn 88-TR detour manifest, when user is not authorized, generate message 43, when cargo is not export type, generate message 31
[28:Container on Flat Car Processing]
Container is not found in primary database → Search container database, if still not found, search inquiry system for container cross-reference, generate error message 11 if no container found
[32:EDI Train List Transmission]
Transmitting to customs system → Call EDI transmission module with train list data, generate error if transmission fails
[37:AEI Activity Logging]
Logging AEI activity → Create log entry with train ID, user ID, date/time, action code 'ZZZ', and AEI send message
[33:Report Transmission to Customs]
Sending report to customs → Send email to OM01247 with train details, equipment list, and status information, handle large reports with continuation logic
[34:Large Report Email Pagination]
Sending large report → Send first portion, create continuation message with headers, and send remaining portions with continuation indicators
[39:Canadian Export Report Generation]
Generating export report → Spawn GCX141 message for export report generation
[43:Duplicate Equipment Removal]
Scanning for duplicates → Remove duplicate car IDs while preserving first occurrence, skip error/warning/info message lines
[44:Activity Audit Logging]
Logging cargo activity → Create audit log entry with cargo CCN, user ID, date/time, action code 'ZZZ', and cargo added message
[Read First Input Message]
The system starts processing → The first input message is read and message availability status is set
[More Input Messages Available?]
The system checks the message availability status → Processing continues if messages are available, otherwise the processing loop terminates
[Classify Request Type - AEI or Regular]
The system examines the request type field → The request is classified as either AEI type or regular type based on the request type value
[Read Next Input Message]
The system attempts to read the next message → The next input message is read and message availability status is updated for the next loop iteration
[End Request Processing Loop]
The system exits the processing loop → The main processing routine is completed and control returns to the calling program
[Cargo Found?]
Cargo retrieval operation completes → If no cargo is found, the no-cargo-found flag is set and error message processing is triggered
[Retrieve Segment 07 Data]
The system retrieves detailed segment information → SEG07 (commodity description), SEG02 (reference numbers), and SEG08 (hazmat) data are retrieved and availability flags are set
[Attach Cargo to Train SEND Action Only]
If cargo for train attachment → Cargo is attached unless it is immediate transport, already created for IT, US-Canada-US with release status, default with release status, empty equipment, or special manifest cargo
[Retrieve Container on Flat Car]
The system searches for container information → Container data is retrieved from FWSWRWR database or inquiry system, and if not found, error message 11 is generated
[Empty Residue Cargo?]
The cargo is classified as empty residue (88-GCUSRT-M1109-EMPTY-RESIDUE) → Skip all error message generation and exit the error processing routine
[No Cargo Found with Residue Weight?]
The equipment is marked as empty → Skip error message generation and exit the error processing routine
[Special Manifest at Woburn-PQ Station?]
The crossing port is Woburn-PQ station → Continue processing without generating error messages
[Special Manifest Special Type?]
The crossing port is NOT Woburn-PQ station → Continue processing without generating error messages
[Is Request Action SEND?]
If the request action type (REQ-ACTION-SEND) → If request action is SEND, proceed to check user authorization for special manifests; if request action is REPORT, generate report message MSG-24
[Create IT Export Special Manifest MSG-23]
The system creates an IT export special manifest → Generate message MSG-23, set IT export spawn flag (WS-IT-EXPORT-SPAWN), and call special manifest creation process (Z870-CREATE-SPECIAL-MANIFEST)
[Generate Report Message MSG-24]
The system processes a REPORT action for IT bond → Generate report message MSG-24 and add it to the report without creating special manifest or spawn processes
[Check User Authorization for Special Manifests?]
The request action is SEND and the system checks user authorization for special manifests → If the user is not authorized for special manifests, set MSG-43 unauthorized message and continue processing without creating the manifest
[Check Request Action = SEND?]
The system checks the request action type → If request action is SEND and user is authorized, create MSG-23 and spawn special manifest; if request action is REPORT, create MSG-24 report-only message
[Set IT Export Spawn Flag]
The system creates the IT export special manifest → Set MSG-23 message type, copy equipment line to report, add equipment to total count, set IT export spawn flag, initialize special manifest parameters with GCX101 IT export type, copy equipment ID, waybill number, waybill date, border codes, CCN from cargo record, origin/destination codes, and queue special manifest for processing
[Check SCAC Access Permission]
The system checks SCAC access permission and the request is an AEI train request → Access is granted even if SCAC access is invalid, but for non-AEI requests with invalid SCAC access, user access is denied and error message 14 is generated
[Validate User Train Send Authority]
The system checks the user's train send authority flag → If user has 'U' or 'S' authorization or the request is an AEI train send, access is granted, otherwise error message 13 is generated and access is denied
[SCAC Access Valid?]
The system validates SCAC access permission for Canadian Pacific (CST-CP-SCAC) through GCCSCAC security module → If SCAC access is invalid AND it is not an AEI train send request, then set access denied message and deny user access
[User Has Send Permission?]
The system checks user's UTF-ADD permission in security profile → If user does not have 'U' or 'S' authorization AND it is not an AEI train send request, then set send permission denied message and deny access
[User Profile Found?]
The system attempts to retrieve the user's security profile from GCSTBRT table using their ACF2 user ID → If the profile is found successfully, load the user security segment data, otherwise initialize an empty security segment
[User Has UTF-ADD Authority?]
The user does not have UTF-ADD authority of 'U' or 'S' AND the request is not an AEI train send request → The system should set message thirteen as active, Execute report index increment, and set user access to denied
[User Profile Found?]
The system performs a database lookup for the user's ACF2 ID in the GCSTBRT-US table → If the profile is found, the system loads the user segment data, otherwise initializes an empty profile with spaces
[Set No User Access - Send Not Authorized]
The request action is SEND and the user's UTF-ADD field is not 'U' or 'S' and the request is not an AEI train send request → The system sets user access to denied, generates error message thirteen, and prevents send operations
[Load User Security Segment]
The system loads user permission data → The security segment data is moved to the user security segment structure
[User Profile Found?]
The system attempts to retrieve user profile from GCSTBRT security table → Load user profile segment if found, otherwise initialize with default empty profile settings
[User Has Send Authority 'U' or 'S'?]
The system checks user's UTF-ADD field for send authority → Allow operation if user has 'U' or 'S' authority OR if request is AEI type, otherwise deny access and generate unauthorized message
[Retrieve Administration Table for MERLIN Configuration]
The system attempts to retrieve administration table with AD key configuration → The administration table segment is retrieved for MERLIN ID extraction
[Extract Public MERLIN ID from Configuration]
The system extracts the public MERLIN ID from the administration segment → The public MERLIN ID value is obtained from the configuration for validation
[Skip Further Equipment Processing]
The error has been added to the report → Further processing of this equipment item is skipped and control returns to process the next equipment
[Retrieve Segment 07 Data]
Detailed cargo information is needed → System retrieves segment 07 (cargo details), segment 02 (reference numbers), and segment 08 (hazmat information) and sets appropriate found/not found indicators
[Attach Cargo to Train]
Cargo attachment processing occurs → Skip attachment for immediate transport cargo, cargo already created for IT, US-Canada-US cargo with release status, default cargo with release status, empty equipment cargo, special manifest cargo at specific stations, or export cargo at non-Laredo stations
[Add TR Bond Warning Message]
Warning message generation occurs → Add message 22 to report with equipment details and increment total equipment count
[Add TE Bond Warning Message]
Warning message generation occurs → Add message 32 to report with equipment details and increment total equipment count
[Add Special Manifest Message]
Special manifest warning generation occurs → Add message 45 to report with equipment details and increment total equipment count
[Add Export Message]
Export warning generation occurs → Add message 51 to report with equipment details and increment total equipment count
[Waybill Not Found and Loaded Equipment?]
Equipment status evaluation occurs → If equipment is loaded and not SBU van type, or if container not found, generate appropriate error messages and build report line
[Create IT Export Special Manifest]
Action is SEND and user is authorized for special manifests → Generate message 23, add report line, set IT export spawn flag, and Execute special manifest creation
[Create TE Port Change Manifest]
Action is SEND and user is authorized for special manifests → Generate message 20, add report line, set port change spawn flag, and Execute special manifest creation
[Create TR Diversion Manifest, Create Border Clearance Manifest]
Action is SEND and user is authorized for special manifests → Generate message 23, add report line, set detour spawn flag, and Execute special manifest creation
[Create US-MX Export Manifest]
Action is SEND and user is authorized for special manifests → Generate message 23, add report line, set 88 TR detour spawn flag, and Execute special manifest creation
[Is Cargo Immediate Transport Bond?]
The cargo is classified as immediate transport bond (M1201 movement type) → The system skips cargo attachment and exits the attachment process
[Is M1201 In-Bond Type Code = 'IT'?]
If the bond type for immediate transport classification → The cargo is classified as immediate transport bond if M1201 in-bond type code equals 'IT' or 'IE'
[Is TR Created for IT = 'Y'?]
If cargo attachment eligibility for immediate transport processing → The cargo is marked for TR created for IT processing if the TR created for IT flag equals 'Y', otherwise cargo attachment is skipped
[Position to First FWIQBOTL Record]
System needs to start reading inquiry bottom line records → System positions to first FWIQBOTL record with segment type 'FWIQBOTL', clears key field, and sets function to GNP
[Set Search Criteria - All Types Except 98-99]
Setting up the car search criteria → Configure to search all car types except types 98 and 99, include all status types, exclude EDI incomplete records, include temporary waybills, exclude corrector waybills, return lead waybill, and use latest waybill date
[Same Waybill Key as Previous?]
The system compares the current FWBX key feedback with the stored previous FWBX key feedback → If the keys match, set waybill not found status and mark as done, otherwise update the stored key and set previous status waybill date for next iteration
[Get Additional Routing Info]
The system processes routing information from FWIQINFO segment → Parse routing fields to extract up to 4 SCAC codes and their corresponding junction R260 codes, handling space-separated field format and storing in routing group structure
[Set Equipment ID as Current]
The system needs to track the current equipment ID for future comparison → The system stores the current equipment ID as the held equipment ID and marks that this is no longer the first call
[Set Retrieval Criteria]
FWCARGET parameters are being configured → The system sets all waybill types except 98 and 99, includes all status types, excludes EDI incomplete waybills, includes temporary waybills, excludes corrector waybills, returns lead waybill, and gets latest waybill date
[Set Previous Status Waybill Date]
The system sets search criteria for previous status → Search parameters are updated to look for waybills with previous status and earlier waybill dates
[First Call or Different Equipment ID?]
The system processes the equipment ID → Store the current equipment ID as the held equipment ID for future comparison AND set the processing flag to indicate this is no longer the first call
[Set Car Retrieval Criteria]
The system sets up retrieval parameters → Configure retrieval to include all car types except 98 and 99 AND include all status types AND exclude EDI incomplete records AND include temporary waybills AND exclude corrector waybills AND return the latest waybill with the most recent date
[Set Previous Waybill Date Processing]
The system prepares to search for previous waybill versions → Set the retrieval parameter to search for previous status waybill date AND update the feedback key tracking with the current waybill feedback key
[Set Retrieval Criteria]
The system initializes FWCARGET parameters → The system sets retrieval criteria to include all waybill types except 98-99, all status types, exclude EDI incomplete waybills, include temporary waybills, exclude corrector waybills, return lead waybill, and get latest waybill date
[Set Previous Waybill Date Status]
The system needs to retrieve an earlier waybill version → The system sets CARGET to previous status waybill date mode
[Retrieve Routing Information]
System accesses FWIQINFO with waybill key and routing segment 'B1' → Retrieve routing information or continue without routing data
[Extract Routing Fields]
System parses routing info fields by spaces → Extract individual routing fields with their lengths for further processing
[Parse SCAC and Junction Data]
System processes each field sequentially → Assign fields to SCAC codes and junction R260 codes in alternating pattern up to 4 SCAC entries
[Build Routing Information Array]
System builds routing information structure → Create routing information array with SCAC and junction pairs for shipment root structure
[IT Bond - Immediate Transport?]
The cargo has immediate transport bond type (IT bond) → Skip cargo attachment and add to special processing queue
[TR Created for IT Bond?]
The cargo has TR bond already created for IT processing → Skip cargo attachment and add to special processing queue
[Is Cargo Immediate Transport Bond?]
The cargo bond type is classified as immediate transport (M1201) → Skip cargo attachment and mark for special processing
[Process Segment 07 Data]
The system processes segment 07 cargo descriptions → Cargo descriptions are extracted from segment 07 data, formatted for display, and multiple descriptions create separate report lines
[Process Car Equipment]
Car processing is initiated → Car ID is set from request equipment ID, load/empty indicator is set from request, car flag is activated, and equipment ID components are parsed
[Analyze SCAC Carrier Patterns]
The system processes consecutive routing entries to identify carrier patterns → The routing information is parsed into SCAC codes and junction codes for pattern analysis
[More Route Segments to Process?]
The system checks for more route segments to process → Processing continues if route segment counter is 9 or less and route has not been found, otherwise processing stops
[Parse SCAC Code from Route Info]
The system parses route segment information → SCAC codes are extracted to route SCAC positions and junction/R260 codes are extracted to corresponding route junction positions
[Bond Type Classification]
If the bond type code from the cargo record → The system should classify the bond as IT (Immediate Transport), TE (Transport Export), TR (Transit), IE (Immediate Export), or MT (Marine Transport) and apply corresponding processing rules
[Generate Loaded Equipment Missing Cargo Message]
System processes equipment with waybill found but cargo not found condition → System generates appropriate missing cargo message for loaded equipment
[Retrieve SHIPCOMM Segment]
System attempts to retrieve SHIPCOMM segment using waybill root key → Retrieve shipment comments data including residue weight and special handling codes for threshold analysis
[Continue Processing - Within Threshold]
Residue weight compliance status is evaluated → Continue normal equipment processing without generating threshold violation errors
[Extract Equipment Description]
Segment 07 contains cargo description information → Extract the cargo description and use it as the cargo information field
[Check if Special Manifest Required]
The system checks user authorization for special manifests → If user is not authorized for special manifests, generate authorization error message 43, otherwise proceed with IT export manifest creation
[Check Port Change Requirements]
The system checks user authorization for port change manifests → If user is not authorized for special manifests, generate authorization error message 43, otherwise proceed with port change manifest creation
[Check Diversion Requirements]
The system checks user authorization for diversion manifests → If user is not authorized for special manifests, generate authorization error message 43, otherwise proceed with diversion manifest creation
[Create IT Export Special Manifest]
The system processes IT export requirements → Generate message 23, set IT export spawn flag, and invoke special manifest creation process
[Create TE Port Change Manifest]
The system processes TE port change requirements → Generate message 20, set port change spawn flag, and invoke special manifest creation process
[Create TR Diversion Manifest]
The system processes TR diversion requirements → Generate message 23, set detour spawn flag, and invoke special manifest creation process
[Request Action Type?]
The request action is evaluated (REQ-ACTION-SEND vs REQ-ACTION-REPORT) → Route to either authorization check for SEND actions or generate report-only message for REPORT actions
[User Authorized for Special Manifests?]
The system checks user authorization flag (WS-USER-NOT-AUTH-4-SPCL-MANIF) → If user is not authorized, generate authorization error message (43), otherwise proceed with special manifest creation
[Generate Special Manifest Creation Message]
IT bond processing requires special manifest creation → Generate message 23 (special manifest creation), set IT export spawn flag, and initiate special manifest creation process
[Generate Report-Only Message]
The request action is REPORT (not SEND) → Generate message 24 (report-only notification) and add equipment line to report
[Request Action = REPORT?]
The request action is REPORT → Generate port change warning message (Message 19) with station information and add to report without creating special manifest
[User Authorized for Special Manifests?]
The system checks user authorization for special manifests → If user is not authorized, generate authorization error message (Message 43) and add to report; if authorized, proceed with port change notification
[Generate Port Change Notification Message]
The system generates port change notification → Create port change notification message (Message 20) and add to report
[Request Action Type?]
If the request action type → If action is REPORT, generate report message; if action is SEND, proceed to authorization check
[Generate Message 18 - TR Bond Diversion Report]
The system processes the diversion for reporting → Message 18 is generated indicating TR bond diversion detected and added to report lines
[User Authorized for Special Manifest?]
The system checks user authorization for special manifest creation → If user is not authorized, generate error message 43; if authorized, proceed with manifest creation
[Generate Message 23 - TR Bond Diversion Send]
The system processes the send request → Message 23 is generated confirming TR bond diversion will be sent and special manifest creation is initiated
[User Authorized for Special Manifests?]
The system checks if the user is authorized for special manifests AND the request is not an AEI train send → If user is not authorized for special manifests, generate authorization error message 43
[Create IT Export Special Manifest]
The request action is SEND → Set IT export spawn flag to TRUE, generate message 23, and Execute special manifest creation process
[Generate IT Export Report Message]
The request action is REPORT → Generate message 24 for IT export reporting
[Create TR Diversion Special Manifest]
The request action is SEND AND user is authorized for special manifests → Set diversion spawn flag to TRUE, generate message 20, and Execute special manifest creation process
[Generate TR Diversion Report Message]
The request action is REPORT → Generate message 19 with station code information for TR bond diversion reporting
[Create TE Port Change Special Manifest]
The request action is SEND AND user is authorized for special manifests → Set port change spawn flag to TRUE, generate message 20, and Execute special manifest creation process
[Generate TE Port Change Report Message]
The request action is REPORT → Generate message 19 with station code information for TE bond port change reporting
[Create US-US Detour Special Manifest]
The request action is SEND AND user is authorized for special manifests → Set US-US detour spawn flag to TRUE, generate message 23, and Execute special manifest creation process
[Generate US-US Detour Report Message]
The request action is REPORT → Generate message 18 for US-US movement detour reporting
[Create US-Mexico Export Special Manifest]
The request action is SEND AND user is authorized for special manifests → Set 88-TR detour spawn flag to TRUE, generate message 23, and Execute special manifest creation process
[Generate US-Mexico Export Report Message]
The request action is REPORT → Generate message 50 for US-Mexico export reporting
[Create Border Clearance Special Manifest]
Cargo status equals release status AND request action is SEND AND user is authorized for special manifests → Set detour spawn flag to TRUE, generate message 23, and Execute special manifest creation process
[Generate Invalid Status Message]
Cargo status does not equal release status → Generate message 31 for invalid cargo status
[Bond Type Requires Special Manifest?]
The system processes the cargo for special manifest requirements → If user is authorized for special manifests or action is not SEND, then create special manifest and generate message 23 or 24, otherwise generate authorization error message 43
[Action Type is SEND?]
The action type is SEND and user is not authorized for special manifests → Generate authorization error message 43 and do not create port change manifest, otherwise if action is SEND and user is authorized, generate message 20 and create port change spawn
[Allow Special Manifest Creation]
The action type is SEND and user is not authorized for special manifests → Generate authorization error message 43 and do not create detour manifest, otherwise if action is SEND and user is authorized, generate message 23 and create detour spawn
[Continue Processing]
Cargo has release status and action type is SEND and user is not authorized for special manifests → Generate authorization error message 43 and do not create detour manifest, otherwise if cargo has release status and action is SEND and user is authorized, generate message 23 and create detour spawn, or if cargo does not have release status, generate message 31
[End Authorization Check]
Cargo does not have special manifest flag and action type is SEND and user is not authorized for special manifests → Generate authorization error message 43 and do not create special manifest, otherwise if action is SEND and user is authorized, generate message 23 and create 88-TR detour spawn, or if cargo has special manifest flag, generate message 31
[Is TR Bond with Export Status?]
The cargo has TR bond type and the cargo status description indicates export status → Generate TR bond export error message
[Is MT Bond at Wrong Location?]
The train crossing port does not match the cargo location ID → Generate MT bond location error message
[Is TE Bond with Wrong Vessel?]
The vessel name does not have 'T' in position 23 → Generate TE bond vessel error message
[Is Non-TE/MT Bond with Wrong Vessel?]
The vessel name is not 'TRAIN' → Generate vessel type error message
[Is Border Hold Status?]
DSP hold is also applied to the cargo → Generate DSP hold error message for border hold cargo
[Is Border Hold Status?]
The cargo description indicates border hold status → Generate border hold error message
[Set Paper 7512 US-CA-US Message]
The cargo bill type code equals '15' → Set the cargo information message to 'PPR 7512 15 US-CA-US'
[Format AMS Bond Message with Bond Number]
The in-bond type code is 'IT' or 'IE' → Format cargo information as 'AMS' followed by the in-bond type code and bond number
[Format AMS 7512 Bond Message with Bond Number]
The in-bond type code is 'TE', 'TR', or 'MT' → Format cargo information as 'AMS 7512' followed by the in-bond type code and bond number
[Accept Bill Type]
No specific bill type formatting rules apply and segment data contains valid information → Extract and format cargo description from segment data into the cargo information field
[Reference Number Qualifier = 'FEN'?]
A reference number qualifier equals 'FEN' → Check if the corresponding reference number value is not empty
[Reference Number Qualifier = 'KCM'?]
A reference number qualifier equals 'KCM' → Check if the corresponding reference number value is not empty
[More Reference Numbers?]
Current reference number processing is complete → If more reference numbers exist, continue processing next reference number, otherwise proceed to documentation validation
[Is DSP Hold Applied?]
The system checks DSP hold application → If DSP hold is applied, generate message 52 for hold at border with DSP hold
[Generate Message 52: Hold at Border with DSP Hold]
The system processes the combined hold conditions → Generate message 52 indicating hold at border status with DSP hold applied
[Is DSP Hold Applied Only?]
The system checks for DSP hold application → If DSP hold is applied, generate message 49 for DSP hold applied
[Generate Message 49: DSP Hold Applied]
The system processes the DSP hold condition → Generate message 49 indicating DSP hold is applied
[Is Hold at Border Status Only?]
If the hold at border condition → Generate message 48 for hold at border status
[Generate Message 48: Hold at Border Status]
The system processes the hold at border condition → Generate message 48 indicating hold at border status
[Generate Message 46: FEN Documentation Required]
The system validates Mexico customs documentation requirements → Generate message 46 indicating FEN documentation is required
[Generate Message 47: KCM Documentation Required]
The system validates Mexico customs documentation requirements → Generate message 47 indicating KCM documentation is required
[User Authorized for Special Manifest?]
The system validates user authorization for special manifests → If user is not authorized, generate error message 43 and report message, otherwise proceed with special manifest creation
[Create Port Change Special Manifest]
The system creates a port change special manifest → Generate message 20, set port change spawn flag, and invoke special manifest creation process
[Create TR Detour Special Manifest]
The system creates a TR detour special manifest → Generate message 23, set detour spawn flag, and invoke special manifest creation process
[Create Border Clearance Special Manifest]
The system creates a border clearance special manifest → Generate message 23, set detour spawn flag, and invoke special manifest creation process
[Create US-MX Export Special Manifest]
The system creates a US-Mexico export special manifest → Generate message 23, set 88-TR detour spawn flag, and invoke special manifest creation process
[Create US-US Detour Special Manifest]
The system creates a US-US detour special manifest → Generate message 23, set US-US detour spawn flag, and invoke special manifest creation process
[Route = CAMX or MXCA?]
The origin-destination country codes equal 'CAMX' or 'MXCA' → Empty equipment error message should be skipped and processing should continue
[User Authorization Check]
The system validates user authorization for special manifests → If user is authorized for special manifests, proceed to request action type check; if user is not authorized, generate authorization error message
[Request Action Type?]
If the request action type → If request action is SEND, proceed to create special manifest spawn; if request action is REPORT, create warning message only
[Create Warning Message]
The system processes the detour requirement → Generate appropriate warning message indicating the detour condition without creating special manifest
[Generate Port Change Warning Message]
The request action is set to REPORT → Generate message nineteen with the current station crossing port code and add the report line to output
[User Authorized for Special Manifest?]
The system checks if the user is authorized for special manifest creation → If not authorized, generate authorization error message and exit; if authorized, proceed with port change processing
[Generate Port Change Processing Message]
All validation criteria are met for port change processing → Generate message twenty, add the report line to output, and prepare for special manifest creation
[Set Port Change Spawn Flag]
The system prepares to create a special manifest for the port change → Set the port change spawn flag to true to trigger special manifest creation
[Request Action Type?]
If the request action type → If action is REPORT, generate warning message 18 for TR bond detour detection; if action is SEND, check user authorization for special manifests
[User Authorized for Special Manifests?]
The system checks if user is authorized for special manifest creation → If user is not authorized for special manifests, generate error message 43 for unauthorized access; if authorized, proceed with special manifest creation
[Generate Warning Message 18]
The system processes the TR bond detour for reporting → Generate warning message 18 indicating TR bond detour detected and add report line to output
[Generate Information Message 23]
The system creates a TR bond special manifest → Generate information message 23 indicating TR bond special manifest created, set detour spawn flag, and add report line to output
[Check Cargo Status Description]
If the cargo short description status → If status equals RELEASE, proceed with detour processing, otherwise generate invalid cargo status message
[Request Action Type?]
The system checks the request action type → If action is REPORT, generate detour report message; if action is SEND, check user authorization
[Generate Message 18 - Detour Report]
The system processes the detour requirement → Generate message 18 indicating detour required and add to report output
[User Authorized for Special Manifest?]
The system validates user special manifest authorization → If user is not authorized, generate authorization error message; if authorized, proceed with manifest creation
[Generate Message 43 - Not Authorized]
The system validates authorization permissions → Generate message 43 indicating user not authorized for special manifest and add to report output
[Generate Message 23 - Special Manifest Created]
The system creates the special manifest → Generate message 23 confirming special manifest creation and add to report output
[Generate Warning Message 18: Original US-US Movement Detour Required]
The system processes the detour for reporting → The system should generate warning message 18 indicating that an original US-US movement detour is required
[Generate Success Message 23: Special Manifest Will Be Created]
The system processes the authorized special manifest request → The system should generate success message 23 indicating that a special manifest will be created
[Generate Report Message 50]
Request action type is 'REPORT' → Generate message 50 and add to report without creating special manifest
[Generate Warning Message 43 - User Not Authorized]
User is not authorized for special manifests → Generate warning message 43 and skip special manifest creation
[Generate Special Manifest Message 23]
User has special manifest authorization → Generate message 23, set 88-TR detour spawn flag, and create special manifest
[Retrieve Container from FWSWRWR Database]
The system searches the FWSWRWR database using the waybill root key → Container segment information is retrieved if found in the database
[Get Next Container Equipment Record]
The system retrieves the next container equipment record using GNP function → Container equipment details are loaded for processing
[Set REPORT Action Header]
Setting the processing result status → If no errors and no warnings, set result as NO MESSAGE, otherwise set result as MESSAGE with warning and error counts including DSP count
[Set Result Status: SENT]
If the final processing status → Set the result status to SENT and count warning messages only
[Any Spawn Activities?]
The system checks for spawn activities → If no spawns exist, check message types for error classification; if spawns exist, check for diversion and IT export messages
[Convert to Message 19 with Station Code]
The system processes spawn message conversion → Convert diversion messages to message 19 and include the station code from GCSTBRT-SC-US-STAT-CODE-X
[Convert to Message 18]
The system processes spawn message conversion → Convert IT export messages to message type 18
[Add Spawn Count to Warning Count]
The system calculates final warning count → Add the spawn count to the existing warning count to get the final warning total
[Is Message Line?]
The system checks if the entry is a message line → The system identifies whether the entry contains message content that needs error type analysis
[Is Spawn Message?]
The system checks if the message is a spawn message → If it is a spawn message, the system skips error counting and continues processing without incrementing counters
[Message Type = Warning?]
If the message type indicator → If the message type is warning, the system proceeds to warning-specific processing and counter increments
[Message Type = Info?]
If the message type indicator → If the message type is information, the system increments the information counter
[Is Warning Type 49 or 52?]
The system checks the specific warning type indicator → If the warning type is 49 or 52, the system increments the DSP counter in addition to the warning counter
[Increment DSP Counter]
The system processes the warning classification → The system increments the DSP counter by 1
[Increment Warning Counter]
The system processes the warning classification → The system increments the warning counter by 1
[Increment Info Counter]
The system processes the information classification → The system increments the information counter by 1
[Adjust Warning Counter Up]
The system adjusts the counters for the conversion → The system increments the warning counter by 1 for each converted message
[Is Message Line?]
The system checks if the entry is classified as a message line → The system identifies whether the entry contains message content that needs further analysis
[Is Spawn Message?]
The message is classified as a spawn message type → The system skips the statistical counting process and continues to index increment
[Add to Report Index]
The message processing is complete → The system increments the report index by one to move to the next entry
[Set Result Status: SENT]
The system determines the final result status → The result status is set to SENT indicating successful transmission to customs
[Set Result Status: NOT SENT]
The system determines the final result status → The result status is set to NOT SENT indicating special processing is required
[Trigger Special Manifest Processing]
The system needs to handle special processing requirements → Special manifest processing is triggered using GCX101 spawn functionality
[Convert Spawn Messages to Diversion Messages]
The system processes messages for final reporting → Spawn diversion messages are converted to message 19 (diversion) and spawn ITE messages are converted to message 18 (detour)
[Add Spawn Count to Warning Count]
The system calculates final warning count for display → The spawn count is added to the existing warning count
[Database Insert Failed - Abend]
The system handles database insert failure → System abend is triggered with appropriate error message
[Set Background Processing Mode]
The EDI transmission process is initiated → The system must be configured for background processing mode
[Call GCCU358T Module for EDI Transmission]
The EDI transmission is executed through GCCU358T module → The train list data must be transmitted to US Customs EDI system
[AEI Train Send Request?]
The system checks the train send type → If the train send is marked as AEI-enabled, additional AEI logging must be performed
[Log AEI Send Activity]
AEI logging is required → The system must create an activity log record with train details, user information, timestamp, and AEI send confirmation message
[Build Report Header with Train Details]
The system prepares the customs report transmission → The report header must include train ID in header line 1, origin station name in header line 1, user ID in header line 2, terminal ID in header line 2, processing date in header line 2, processing hour in header line 2, and processing minute in header line 2
[Set US Customs Train ID]
The system builds the report header for customs transmission → The US customs train ID from the train list must be assigned to header line 4
[Set ETA Date and Time Fields]
The system builds the report header for customs transmission → The ETA year must be set in header line 4, ETA month must be set in header line 4, ETA day must be set in header line 4, ETA hour must be set in header line 4, and ETA minute must be set in header line 4
[Add Equipment Total Count to Status Line]
The system prepares the status line for customs transmission → The total equipment count must be moved to the status line and the status line must be assigned to email text line 5
[Format Report Lines for Email]
The system prepares the email transmission to customs → Report line 1 must be copied to email text line 1, report line 2 must be copied to email text line 2, report line 3 must be copied to email text line 3, report line 4 must be copied to email text line 4, detail header 1 must be copied to email text line 6, and detail header 2 must be copied to email text line 7
[Set Email Parameters]
The system prepares the email parameters → Keywords must be set to spaces, copy user code must be set to spaces, item number sequence must be set to spaces, item alpha sequence must be set to spaces, and return status flag must be initialized
[Set Sender as OM01247]
The system sets the email sender and recipient → The from user code must be set to 'OM01247' and the to user code must be set to 'OM01247'
[Set Email Width to 80 Characters]
The system sets the email formatting parameters → The email item width must be set to '080' characters
[Report Size Check]
The system processes report lines for email transmission and the line count reaches 700 lines → The system must send the current email batch, reset the email text, initialize line counter to zero, add continuation message as line 1, add detail header 1 as line 2, add detail header 2 as line 3, and increment line counter by 3
[Split Report into Multiple Emails]
The system reaches the line limit → The system must send the current email batch, clear the email text, reset line counter, add continuation message, add report headers, and continue processing remaining lines
[Handle Email Send Failure]
The system detects the email send failure → The system must set the error message to 'SEND TO FILE OF OM01247 FAILED' and Execute system abend
[Purge Message Queue]
The system completes the email transmission → The system must initialize the accept status and call CIMS with PURG to purge the alternate PCB message queue
[Format REPORT Header with Message Counts]
The system formats the REPORT header → Header line 3 is marked as REPORT type, and if no errors and no warnings then result is set to no messages, else result is set to show messages with warning count and error count populated
[Split Report into Multiple Email Parts]
The system splits the report → No-more-email flag is set to true, current email segment is sent, email text is cleared, and line counter is reset to zero
[Add Continuation Header for Next Part]
The system adds continuation header → Continuation message is added to line 1, detail header 1 is added to line 2, detail header 2 is added to line 3, and line counter is incremented by 3
[Format Single Email with All Content]
The system formats single email → Complete report content is prepared for transmission in single email message
[Check Line Counter > 699?]
The line counter exceeds 699 lines in the current email message → The system should send the current email batch, clear the message buffer, reset the line counter, and add continuation headers for the next batch
[Add Current Line to Email Message]
The system processes the current report line → The report line should be added to the email message buffer at the current line position
[Increment Line Counter]
The line addition is complete → The line counter should be incremented by one to track the current message size
[Send Current Email Batch via EMCSEND3]
The pagination limit is reached or all lines are processed → The system should invoke EMCSEND3 to transmit the email batch to the designated recipients
[Clear Email Message Buffer]
The system needs to prepare for the next batch of report lines → The email message buffer should be cleared and reset to spaces
[Add Continuation Header Line]
The system starts a continuation email → A continuation header message should be added as the first line indicating this is a continuation of the report
[More Report Lines to Process?]
A line has been processed or a batch has been sent → The system should check if more report lines exist to determine whether to continue processing or finalize the email transmission
[Send Final Email Batch]
No more report lines remain to be processed → The system should send the final email batch containing the remaining report lines
[Split Email into Batches]
The system processes the email for transmission → The system sets no-more-email flag to true, clears the message buffer, resets line counter to zero, and prepares continuation header with report headers
[Handle Transmission Failure]
The system processes the transmission failure → The system clears the primary recipient, sets fallback recipients to 'AEI9999' and 'OM01247', and attempts retransmission
[Call EMCSEND3 for Current Batch]
The system needs to send the email → The system calls EMCSEND3 service with sender ID, destination filename, recipient addresses, subject, keywords, message content, and formatting parameters
[Purge Message Queue]
The system finalizes the email process → The system initializes accept status and calls CIMS with PURG function to purge the alternate PCB message queue
[Call EMCSEND3 for Current Batch]
The system calls EMCSEND3 transmission module → The email is transmitted with FROM usercode, destination filename, TO usercode, copy usercode, subject, keywords, message text, item formatting parameters, and transmission status is returned
[Transmission Successful?]
The transmission return status is evaluated → If return status indicates success, continue normal processing; if return status indicates failure, initiate error notification process
[Clear Message Buffer]
The system prepares for the next batch → Message buffer is cleared, continuation header 'CONTINUATION OF REPORT ....' is added, detail headers are added, and line counter is reset to 3
[System Abend]
The system cannot recover from email transmission failures → System abends with error message 'SEND TO FILE OF OM01247 FAILED'
[Set Email Headers and Subject]
Email headers and subject are being configured → The system shall set the sender and recipient to OM01247, clear keywords and copy fields, use the first report line as the subject, and clear item sequence numbers
[More Report Lines to Process?]
The system checks for remaining lines to process → The system shall continue processing if the current line is not empty or low-values and the maximum email line limit has not been exceeded
[Add Line to Email Message]
The line is added to the email message → The system shall copy the report line to the corresponding email text line position
[Increment Line Counter]
The line counter is updated → The system shall increment the line counter by one and set the email continuation flag to indicate more content exists
[Send Current Email Batch]
The email send operation is executed → The system shall call the email service with all configured parameters including sender, recipient, subject, content, and formatting options
[Email Send Successful?]
If the transmission result → The system shall check the email return status flag to determine if the transmission was successful
[Handle Email Failure]
The failure handling process is initiated → The system shall clear the recipient usercode field and prepare alternative recipient addresses for error notification
[Reset Email Message Buffer]
The message buffer is reset for continuation → The system shall clear the email text content and reset the line counter to zero
[Add Continuation Header]
Continuation headers are added → The system shall add 'CONTINUATION OF REPORT ....' as the first line and increment the line counter to 1
[Send Final Email Batch]
The final email transmission is executed → The system shall send the email using the same transmission service with all configured parameters
[Log Email Success]
Success logging is performed → The system shall record the successful transmission without generating error messages
[Purge Message Queue]
Message queue purging is performed → The system shall clear the accept status and call the message purge service to clean up communication resources
[Add Report Line to Email Message]
The line is processed for inclusion → The report line is moved to the email text message line at the current line subscription position AND the line subscription counter is incremented by 1 AND the more email flag is set to true
[Send Current Email Batch]
The batch size limit is reached → Call EMCSEND3 to send the current email batch with all configured parameters including sender, recipient, subject, and message content
[Clear Email Message Buffer]
The system prepares for the next batch → Clear the email text message buffer by setting it to spaces
[Reset Line Counter to Zero]
Preparing for the next batch of lines → Set the line subscription counter to zero
[Add Continuation Header]
The continuation header needs to be added → Add 'CONTINUATION OF REPORT ....' message to the first line of the new email batch
[Add Report Detail Headers]
Detail headers need to be added after the continuation message → Add the standard detail header line 1 to email text message line 2 AND add the standard detail header line 2 to email text message line 3
[Report Size Exceeds Limit?]
The report exceeds 699 lines → The report is split into multiple emails with continuation headers and the current email is sent before starting a new one
[Report Display Mode?]
If the report should show all details or selective content → All report lines are sent for comprehensive reports, or selective content is sent based on warning conditions
[Report Status?]
The report transmission status is evaluated → Generate 'NOT SENT' subject line for errors or failed transmissions, otherwise generate 'SENT' subject line for successful transmissions
[Generate _NOT SENT_ Subject]
Generating the email subject line → Create subject line with format 'US TRAIN [train_id] NOT SENT AT [origin]' using report header train ID and origin
[Send Current Email Batch]
Sending the current email batch using EMCSEND3 → If send fails, redirect to error notification addresses AEI9999 and OM01247, otherwise continue processing
[Start New Email with Continuation Header]
Starting a new continuation email → Clear email text, reset line counter to 1, add continuation message, and add detail headers starting at line 3
[Send Final Email Batch]
Sending the final email batch using EMCSEND3 → If send fails, redirect to error notification addresses AEI9999 and OM01247
[Log Email Failure]
The system cannot send any email notifications → Generate system error message 'SEND TO FILE OF OM01247 FAILED' and Execute system abend
[Set Standard AEI Send Message]
The message field needs to be populated → The standard AEI send log message is assigned to describe the activity
[Prepare Log Message for Queue]
The log entry needs to be queued for processing → The log input structure is moved to the message format for queue transmission
[Send Log to Message Queue]
The log needs to be sent to the queue system → The system calls the message queue service to transmit the log entry
[Write Log Message to System]
The log message needs to be written to system storage → The system writes the log message using the message logging service
[Purge Message Queue]
Queue cleanup is required → The message queue is purged to remove the processed log entry
[Set Message Function Name Flag]
The system configures the message function type → The message function name flag is set to indicate export report generation
[Set Security Byte to High Values]
The system sets security parameters for the message → The security byte is set to high values to ensure proper authorization level
[Move US Customs Train ID to Message]
The system populates the train identifier in the message → The US customs train ID from the train list is assigned to the GCX141 train ID field
[Set Message Function Length Flag]
The system finalizes message configuration → The message function length flag is set to indicate proper message sizing
[Move Input Parameters to Message Output]
The system prepares the message for transmission → The complete GCX141 input structure is moved to the message output text field
[Insert GCX141 Message to Queue]
The system sends the message to the GCX141 processing queue → The message is inserted into the queue for Canadian export report generation
[Email Message Size Limit Reached?]
The system checks if message size limit is reached → If line count exceeds 699 lines, send current batch and initialize continuation email with headers
[Start PDF Report Generation]
The system starts the PDF generation process → The report message data should be cleared to prepare for new content
[Prepare Pre-Exit Report Data]
Preparing the report data → The report message should be populated with the existing email text content and email subject should be set from the first report line
[Prepare Export Train Report Data]
Preparing the report data → The report message should be populated with the new report table content and email subject should be set from the new report subject
[Check Special Conditions]
The crossing port is Woburn PQ station → Continue processing without generating error messages
[Check Special Conditions]
The crossing port is not Woburn PQ station → Continue processing without generating error messages
[Categorize Message Type]
The message type is determined → Set appropriate error, warning, or info flag and increment corresponding counter
[Is Spawn Message?]
The message is identified as a spawn message → Skip all message type classification and counting processes
[Check if Message Type 43]
The message type indicator equals 43 → Increment the type 43 error count by 1
[Warning Message?]
The message is classified as a warning message (MSG-WRN) → Increment the total warning count by 1
[DSP Message Type 49 or 52?]
The message type indicator equals 49 or 52 → Increment the dispatcher count by 1
[Information Message?]
The message is classified as an information message (MSG-INF) → Increment the total information count by 1
[Is Message Line?]
The system checks if the entry is a message line → The system identifies whether the entry contains a message that needs to be classified for counting purposes
[Is Spawn Message?]
The system checks if the message is a spawn message → Spawn messages are excluded from error, warning, and information counting but still increment the report index
[Is Message Type 43?]
The error message type is 43 (authorization failure) → The system increments the special error count 43 by 1 in addition to the general error count
[Is Message Type 49 or 52?]
The warning message type is 49 or 52 (DSP hold conditions) → The system increments the DSP hold count by 1 in addition to the general warning count
[Information Message - Add to Info Count]
The message is classified as an information type → The system increments the information count by 1
[Increment Report Index]
The system completes message processing → The report index is incremented by 1 to point to the next available report line
[Set Report Overflow Message]
A report overflow condition is detected → The system sets message type 9 (report overflow) to notify users that the report is truncated
[Is Spawn Message?]
The message is classified as a spawn message type → Skip the severity classification and counter increment processing but continue with report index addition
[Classify as Warning Message]
The message severity is classified as warning level → Increment the warning counter by 1, and if the message type is 49 or 52, also increment the DSP counter by 1
[Classify as Information Message]
The message severity is classified as information level → Increment the information counter by 1
[Report Line Limit Reached?]
The report index is incremented by 1 → If the maximum report line limit is reached, set message type 9 (overflow message) at the current report index position
[Is Message Line?]
The report line is not identified as a message line → The system skips message classification and continues processing without incrementing any counters
[Is Spawn Message?]
The message is identified as a spawn message → The system skips severity classification and continues processing without incrementing any counters
[Skip Counter Update]
The message line is identified as a spawn message type → The system skips all counter updates and proceeds to report index management
[Increment ERR-43 Counter]
The message type indicator equals 43 → The system adds 1 to the ERR-43 counter in addition to the general error counter
[Increment Warning Counter]
The message type is determined to be a warning → The system adds 1 to the warning message counter
[Increment DSP Counter]
The message type indicator is 49 or 52 → The system adds 1 to the DSP counter in addition to the warning counter
[Increment Info Counter]
The message type is determined to be informational → The system adds 1 to the informational message counter
[Update Report Index]
Counter processing is complete → The system adds 1 to the report line index
[Remove duplicate car entries from reports while preserving messages]
The system scans through report lines up to position 700 and encounters equipment entries with car IDs → The system should remove duplicate car ID entries while preserving all message lines (error, warning, information) and maintain the first occurrence of each unique car ID
[Get Current Report Line]
A report line contains an empty car ID or represents a message line with prefixes 'ERR>', 'WRN>', or 'INF>' → The system should skip processing this line and continue to the next report line without any duplicate checking
[Store Car ID as Previous]
The car ID is not empty and not a message line → The system should store this car ID as the new reference for subsequent duplicate comparisons
[Set Log Message Type]
The system categorizes the type of audit message → The message type is set to the predefined 'CAR-ADDED-LOG-MESSAGE' to indicate cargo addition activity
[Format Complete Log Message]
The system prepares the final audit message → The complete GCX105 input structure is moved to the GCT1051E message format for transmission
[Send Log to Message Queue]
The system sends the message to the queue → The message is sent using CIMS with CHNG function to the alternate PCB for the GCT1051E message type
[Write Log Message to System]
The system writes the message to the system log → The message is written using WRITMSGL with the message code, content, length, and module name
[Purge Message Queue]
The system completes the logging process → The message queue is purged using CIMS with PURG function to clean up the alternate PCB
[Lookup Port in Reference Table]
The system needs to determine port automation status → Look up the port configuration in GCSTBRT SS segment using cargo SCAC and station code
[Process Segment 07 Equipment Descriptions]
The system processes segment 07 entries → Each valid segment 07 description is formatted as a separate report line with equipment totals incremented
[Call Cargo Segment Retrieval Service]
The system calls the cargo segment retrieval service GCCUSIO2 → The system retrieves all requested segments (07, 02, 08) and their associated data arrays in one service call
[Move Retrieved Segment 07 Data to Working Storage]
The system processes the retrieved segment data → The system moves the first occurrence of segment 03, 06, 07, 08, 09, and 12 data from arrays into individual working storage variables
[Loop Through All Segment 07 Entries]
The system processes segment 07 entries sequentially from 1 to maximum sequence number → For each entry that is not spaces or low-values, extract commodity description, create report line, add to equipment count if first entry, and continue until all entries processed or report maximum reached
[Extract Commodity Description from Each Entry]
The system processes the segment 07 entry for report generation → The system moves the segment 07 data to working storage, extracts the commodity description field, and formats it for report display
[Retrieve Station Table Information]
The system retrieves station table data using commodity code ID and 'ST' qualifier → If station table data is found successfully, move data to station segment working storage, otherwise set station segment to spaces
[Check for Special Freight Equipment Type]
The system processes station type entries from 1 to 3 and finds type code 'SFE' with country 'US' or spaces → If report info is not spaces, add current report line to output and increment report index, then move station type description to report info and set segment indicator to N
[Check Special Manifest Original]
Special manifest original flag is not set → If action is SEND and user is not authorized for special manifest, generate error message 43, otherwise generate message 23 and set IT export spawn flag for special manifest creation
[Check Special Manifest Requirements]
Cargo short description equals release status → If action is REPORT, generate message 18, otherwise if action is SEND and user is not authorized for special manifest, generate error message 43, otherwise generate message 23 and set detour spawn flag
[Check Special Manifest Requirements]
Action is REPORT → Generate message 50, otherwise if action is SEND and user is not authorized for special manifest, generate error message 43, otherwise generate message 23 and set 88 TR detour spawn flag
[Create IT Export Special Manifest]
Special manifest original flag is set (GCUSRT-SPECIAL-MFST-ORIG is true) and user is authorized for special manifests → Create IT export special manifest, generate message 23, and spawn GCX101 process with IT export flag
[Create TE Bond Special Manifest]
TR was not created for IT (GCUSRT-TR-CREATED-FOR-IT not = 'Y') and cargo status is not export and cargo is billed as CPRS and port location differs from manifest location → Create port change special manifest, generate message 20, and spawn GCX101 process with port change flag
[Create TR Bond Diversion Special Manifest]
TR was not created for IT (GCUSRT-TR-CREATED-FOR-IT = SPACES) and cargo status equals release status (GCUSRT-RT21-USCARGO-SHORT-DESC = WS-GCUSRT-RT21-USCARGO-RELEASE) → Create detour special manifest, generate message 23, and spawn GCX101 process with detour flag
[Create Border Clearance Special Manifest]
TR was not created for IT (GCUSRT-TR-CREATED-FOR-IT = SPACES) and cargo status equals release status and special manifest original flag is not set → Create detour special manifest, generate message 23, and spawn GCX101 process with detour flag
[Create US-MX Export Special Manifest]
Special manifest flag is spaces (GCUSRT-USMX-SPECIAL-MFST = SPACES) and does not have special 88 flag → Create 88 TR detour special manifest, generate message 23, and spawn GCX101 process with 88 TR detour flag
[Create US-US Movement Special Manifest]
Equipment is loaded or equipment is empty with residue weight greater than zero and residue found and not conveying car → Create US-US detour special manifest, generate message 23, and spawn GCX101 process with US-US detour flag
[Create Port Change Special Manifest]
Cargo location (GCUSRT-M1203-LOCATION-ID1) differs from train crossing port (GCSTBRT-SC-US-STAT-CODE-X) and action is send and user is authorized for special manifests → Create port change special manifest, generate message 20, and spawn GCX101 process with port change flag
[Create TR Diversion Special Manifest]
Train crossing port (GCSTBRT-SC-US-STAT-CODE-X) differs from cargo location (GCUSRT-P401-LOCATION-ID) and action is send → Create diversion special manifest, generate message 20, and spawn GCX101 process with diversion flag
[Format Equipment Description from Segment 07]
Segment 07 data entry is not spaces or low-values → Use segment 07 SED field as equipment information description
[Process Multiple Description Lines]
Processing each segment 07 entry that is not spaces or low-values → Create separate report line for each description and increment equipment counter only for first description
[Set Segment Types: SEG07, SEG02, SEG08]
The system configures segment types for retrieval → The system should set flags to retrieve SEG07 equipment descriptions, SEG02 reference numbers, and SEG08 hazmat data
[Call GCCUSIO2 to Retrieve Segments]
The system calls the cargo I/O module to retrieve segment data → The system should execute the database call to fetch SEG07, SEG02, and SEG08 segment information
[Move Retrieved Data to Working Storage Arrays]
The system processes the retrieved data → The system should move SEG03, SEG06, SEG07, SEG08, SEG09, and SEG12 data from arrays to individual segment structures
[SEG07 Data Found?]
The system checks for SEG07 data availability → The system should set SEG07-FOUND flag if data exists or SEG07-NOT-FOUND flag if data is spaces or low-values
[Check SEG07 Data Availability]
The system checks for SEG02 data availability → The system should set SEG02-FOUND flag if data exists or SEG02-NOT-FOUND flag if data is spaces or low-values
[Check SEG07 Data Availability]
The system checks for SEG08 data availability → The system should set SEG08-FOUND flag if data exists or SEG08-NOT-FOUND flag if data is spaces or low-values
[Parse Container Cross-Reference Information]
Inquiry bottom line record contains 'T/C XREF' in first 8 characters → Container ID is extracted from positions 28-39, road number from positions 10-12, station number from positions 14-19, and waybill number from positions 21-26
[Set Container Found from Inquiry System]
At least one valid container ID is extracted from cross-reference data → Container found status is set to true and container IQ found status is set to true with first container ID assigned as equipment ID
[Set AEI Send Flag]
The request type indicates AEI transmission → The AEI send flag is set to true, otherwise it is set to false
[More Equipment to Process?]
Checking for more equipment items → Continue processing if report index is within bounds, equipment table is not full, and current line contains valid equipment data (not message, end report, or blank line)
[Check Processing Status]
There are errors or warnings → Set message result flag, populate warning count, populate error count, and populate DSP count
[Set Result Status: SENT]
There are no processing errors AND there are no spawn messages → Set result status to SENT AND record warning message count
[Set Result Status: NOT SENT]
There are spawn messages present → Set result status to NOT SENT AND count warning messages AND add spawn count to error count AND set total error count
[Trigger Special Manifest Processing]
Spawn messages need to be processed → Execute special manifest processing for each spawn message from 1 to spawn count
[Convert Spawn Messages to Report Messages]
Message lines contain spawn division messages:
spawn ITE messages
→ Convert spawn division messages to message nineteen with station code AND convert spawn ITE messages to message eighteen
[Convert Spawn Messages to Warning Messages]
Final message processing occurs → Add spawn count to warning message count
[Convert Spawn Messages to Report Messages]
Total error count equals the count of type 43 errors → Convert message 43 to message eighteen AND increment warning count AND decrement error count
[Set Result Status: NOT SENT]
Final result classification is performed → Set result status to NOT SENT AND record final warning message count AND record final error message count
[Finalize Report Headers and Summary]
The system finalizes the report for transmission → The system sets the end report marker if the last line is blank, records the last line index, creates header lines with train ID and origin station, adds user ID and terminal information with current date and time, and formats the result status based on the request action type
[Evaluate Request Action Type]
If the request for final processing → If the action is SEND with no errors and no spawns, Execute full transmission processing; if the action is REPORT, Execute report-only processing; otherwise Execute error handling with database rollback
[Transmit Train List to US Customs EDI]
The system transmits the train information to customs → The system calls the customs EDI transmission module (GCCU358T) in background mode with the complete train list data, and if AEI send flag is set, logs the AEI transmission activity
[Remove Duplicate Equipment Entries]
The system scans for duplicates → For each equipment entry, if the car ID matches the previously held car ID, clear the current car ID to spaces; otherwise update the held car ID with the current car ID, excluding error, warning, and information message lines from duplicate checking
[Generate PDF Report]
The system generates the PDF report → The system calls the PDF generation module (GCX904R) with the report message content, email subject from the first report line, train ID, report title as 'Pre-Exit Report', report type as 'EXPORT', PDF length of 80 characters, and the total number of report lines
[Spawn Canadian Export Report]
The system spawns the export report → The system creates a GCX141 message with function name flag, train ID, and message length, then inserts the message to trigger the Canadian export report generation process
[Set Acknowledgment Only Flag]
The system prepares the originator response → The system sets the acknowledgment only flag to true to indicate that only a brief confirmation should be sent rather than the full detailed report
[Send Report to Originator Terminal]
The system sends the response to the originator → If AEI send flag is set, send AEI-specific report; determine destination terminal from alternate terminal or original terminal; set call letters based on error status and action type; send header line first, then send appropriate report content based on acknowledgment flag and warning status, and finally send wrap-up message
[Send Activity Audit Logs]
The system generates audit logs → For each added US CCN (up to 2499 entries), create a log entry with security byte, US cargo flag, action code 'ZZZ', sending transaction 'GCT0031E', user ACF2 ID, current date and time, the US CCN key, and car added log message, then transmit the log entry
[Transmit Train List to US Customs EDI]
The system processes the transmission step → Call GCCU358T module to transmit the train list data via EDI to US Customs
[Spawn Canadian Export Report]
The system processes export reporting → Send message to GCX141 queue to spawn Canadian export report processing
[Send Activity Audit Logs]
The system creates audit trails → For each added US CCN, create audit log entry with user ID, timestamp, and cargo addition message via GCT1051E
[REPORT Action?]
The system processes the report-only request → Execute duplicate removal and send report to originator without database storage or EDI transmission
[Set RPT-RESULT-SENT Status]
The system sets the transmission result status → The result status is set to SENT and warning count is recorded
[Set RPT-RESULT-NO-SENT Status]
If the transmission eligibility → The result status is set to NO-SENT, spawn count is added to error count, and special manifest processing is prepared
[Set RPT-RESULT-NO-SENT Status]
If the transmission eligibility → The result status is set to NO-SENT and both warning and error counts are recorded
[Check REQ-ACTION-SEND]
If the request action type for send operations → The system determines whether to proceed with customs transmission or generate reports only
[Check REQ-ACTION-REPORT]
If the request action type for report operations → The system determines whether to generate reports without customs transmission
[Set Processing Result: SENT]
The system determines the final processing result → The system sets the processing result to SENT indicating successful customs transmission
[Set Processing Result: REPORT GENERATED]
The system determines the final processing result → The system sets the processing result to REPORT GENERATED indicating successful report creation without customs transmission
[Message Line Type?]
If the report line type → The system identifies whether the line is a message line requiring error count processing or a non-message line to be skipped
[Spawn Message?]
The system checks if the message is a spawn message type → Spawn messages are excluded from error counting while non-spawn messages proceed to error type classification
[Increment Type 43 Counter]
The system processes the Type 43 error → The ERR-43-CNT counter is incremented by one
[Increment Warning Counter]
The system processes the warning message → The report warning counter is incremented by one
[Warning Type 49 or 52?]
The system checks if the message type indicator is 49 or 52 → Warning types 49 and 52 additionally increment the DSP counter by one
[Increment DSP Counter]
The system processes the special warning type → The RPT-DSP-CNT counter is incremented by one
[Increment Info Counter]
The system processes the information message → The report information counter is incremented by one
[SEND Action Processing]
The system processes the SEND action → The system must store train list in database, transmit via EDI, check for duplicates, send reports to customs, generate export reports, send acknowledgment to originator, and create audit logs
[Transmit Train List via EDI]
The system transmits the train list via EDI → The complete train manifest must be sent to customs system via GCCU358T module in background mode, and if AEI send is enabled, an AEI send log entry must be created
[Generate Enhanced Format Reports]
The system generates enhanced format reports → A GCX141 message must be created with the US customer train ID and sent via message queue for enhanced report generation
[Create Activity Audit Logs]
The system creates activity audit logs → For each added cargo record, a log entry must be created with US cargo type, action code ZZZ, sending transaction GCT0031E, user ACF2 ID, current date and time, cargo CCN number, and cargo added message
[Extract Equipment Details]
Extracting equipment details from report → If report line is not a message line AND not an end report line AND not a blank line, then increment equipment quantity and extract equipment information
[Call GCCU358T Module for EDI Transmission]
The EDI transmission is executed → The GCCU358T module must be called with the complete train list data for transmission to US Customs
[AEI Train Send Request?]
The system checks the request type → If the request is an AEI train send request, additional AEI logging must be performed AND if not an AEI request, complete the transmission process normally
[Log AEI Send Activity]
AEI logging is performed → The system must create an activity log entry with train ID, user information, timestamp, and AEI send confirmation message
[Complete EDI Transmission]
The transmission process is finalized → The EDI transmission process must be marked as complete and control returned to the calling process
[System Abend - Invalid Parameters]
The parameter validation fails → The system must initiate an abend condition with the specific error message indicating invalid GCCU358T module parameters
[Set NO MESSAGE Result]
There are no errors (RPT-NO-ERROR) and no warnings (RPT-NO-WRN) → Set the result status to no message
[Set MESSAGE Result with Counts]
There are errors or warnings present → Set result status to message, populate warning count, error count, and DSP count in the header
[Set Result Status: SENT]
The system determines the final processing result status → Set the result status to SENT and record warning count for reporting
[Set Result Status: NOT SENT]
The system determines the final processing result status → Set the result status to NOT SENT, add spawn count to error count, and trigger special manifest processing
[Count Warning Messages]
The system prepares the final result classification → Count all warning messages and record the warning count in the result status
[Trigger Special Manifest Processing]
The system needs to process spawned items → Execute special manifest processing for each spawned item using GCX101 module
[Update Message Counts]
The system finalizes message counts for reporting → Increment warning count by 1 and decrement error count by 1 for each converted message
[Generate Report Header with Status]
The system generates the final report header → Create report header line 4 with train ID, ETA information, and set the appropriate result status (SENT, NOT SENT, or ABORTED) with final warning and error counts
[Add Line to Email Message]
The system processes the report line for email inclusion → The report line is added to the email message buffer and the line counter is incremented by 1
[Send Current Email Batch]
The batch size limit is reached → The email is sent using EMCSEND3 service, the message buffer is cleared, and the line counter is reset to zero
[Add Continuation Header]
The system initializes the continuation email → A continuation message 'CONTINUATION OF REPORT ....' is added as the first line, followed by report detail headers, and the line counter is incremented by 3
[Report Display Mode?]
The system checks the report display mode setting → The system sends all report lines if set to all report mode, otherwise sends summary based on warning status
[Has Warnings?]
The system checks if the report contains warning messages → The system sends only header lines if no warnings exist, otherwise sends header plus all warning message lines
[Send Report Header Line]
The system initiates report transmission → The system sends the report header line containing report identification and formatting information
[Send All Report Lines]
The system processes report line transmission → The system iterates through and sends every report line from first line to last line
[Send Header Lines Only]
The system determines report content to transmit → The system sends only the first four header lines containing basic report information
[Send Warning Messages Only]
The system scans through report lines to identify warnings → The system processes each warning message line and its preceding context line for transmission
[Send Report Wrap Command]
The system completes report line transmission → The system sends a wrap command with user function code to properly terminate the report session
[Load Report Lines into Email]
The system loads report content into email message → Each report line is copied to email text lines sequentially, with line counter incremented, and email-more flag set to true
[Email Size Limit Reached?]
The email line count exceeds 699 lines → The system sets no-more-email flag, sends current email batch, clears email text, resets line counter to 1, and adds continuation header lines
[Send Current Email Batch]
The system sends the email batch → The email is transmitted to inbox destination using sender ID, recipient list, subject line, and message content through the email service
[Set Log Message as 'AEI SEND LOG MESSAGE']
The log message content needs to be assigned → The message field is set to the predefined 'AEI SEND LOG MESSAGE' constant
[Format Log Record for GCT1051E]
The record needs to be prepared for transmission → The log input structure is formatted and moved to the GCT1051E message format
[Send Log Record to Message Queue]
The record needs to be sent to the logging system → The system calls the message processing service to change the alternate PCB and queue the log record
[Write Log Message to System]
The record needs to be permanently logged → The system calls the message writing service with the log message code, content, length, and module name
[Purge Message Queue]
The logging transaction needs to be completed → The system calls the message processing service to purge the alternate PCB and complete the transaction
[Set Message Function Name Flag]
The system configures the message type → The message function name flag is set to TRUE
[Set Security Byte to High Values]
Security parameters need to be established → The security byte is set to high values for maximum security clearance
[Move US Customs Train ID to GCX141 Train ID]
A Canadian export message is being prepared for that train → The US customs train ID is copied to the GCX141 train ID field
[Set Message Function Length Flag]
Message length parameters need to be configured → The message function length flag is set to TRUE
[Move GCX141 Input to Message Output Text]
The message needs to be prepared for output → The complete GCX141 input is moved to the message output text field
[Insert GCX141 Message to Queue]
The message needs to be queued for processing → The GCX141 message is inserted into the processing queue via Z750-ISRT-GCX141-MSG procedure
[Line Count > 699?]
The line count reaches 699 lines → The current email batch is sent, email buffer is reset, continuation header is added, and processing continues with remaining lines
[Send Email Batch]
The system sends the email batch → Email is sent to OM01247 usercode with 80-character line width and appropriate subject line containing train ID
[Is Message Line?]
The system checks if the line contains a message using the message line indicator → The system identifies whether the line is a message line that requires classification or a regular report line that should be skipped for message counting
[Is Spawn Message?]
The system checks if the message is a spawn message type → If it is a spawn message, skip the message counting process and proceed to increment report index, otherwise continue with message classification
[Check if Message Type 43]
The message type indicator equals 43 → The system increments the Type 43 error count by 1 in addition to the general error count
[Increment Warning Count]
The message type is classified as a warning message → The system increments the warning count by 1 for report statistics
[Warning Type 49 or 52?]
The message type indicator equals 49 or 52 → The system increments the DSP count by 1 in addition to the general warning count
[Increment Info Count]
The message type is classified as an informational message → The system increments the information count by 1 for report statistics
[Increment Report Index]
The system completes processing of the current report line → The system increments the report index by 1 to move to the next report line position
[Set Overflow Message]
The system detects report overflow condition → The system sets message type 9 (overflow message) at the current report index position to indicate report truncation
[Add Line to Email Message]
A report line needs to be added to the email → The report line is moved to the email text message line at the current line position
[Increment Line Counter]
Line counting needs to be updated → The line counter is incremented by 1 and email status is set to 'More Email'
[Send Current Email Batch]
Email batch sending is triggered → The email is sent using EMCSEND3 with all configured parameters and accumulated message lines
[Clear Email Message Buffer]
Email message buffer needs to be cleared → The email text message buffer is cleared to spaces
[Add Continuation Header Line]
Continuation header needs to be added → The message 'CONTINUATION OF REPORT ....' is added as the first line of the new email batch
[Add Report Detail Headers]
Report structure headers need to be included → Report detail header lines are added to the email message to maintain column structure
[Send Final Email Batch]
Final email transmission is required → The final email batch is sent using EMCSEND3 with all remaining accumulated message lines
[System Abend - Email Send Failed]
The email delivery validation detects the failure → The system should set an error message indicating 'SEND TO FILE OF OM01247 FAILED' and Execute an abend to halt processing
[Set Cargo Segment Type]
The system prepares for cargo record access → The cargo segment type is set to target cargo records in the database
[Set Database Function Code]
The system determines the type of database operation needed → The appropriate function code is set for get first (GU), get next (GN), or replace (REPL) operations
[Extract Container Cross-Reference Data]
The system processes FWIQBOTL segments to extract container cross-reference data → Identify and extract container IDs, waybill railroad, station, and number information from T/C XREF entries
[Get Routing Information from Inquiry]
The system retrieves routing information from FWIQINFO with segment type B1 → Extract and parse routing fields including SCAC codes and junction information, then format into routing groups
[Same Waybill Key as Previous?]
The system compares the current waybill key feedback with the previously stored waybill key feedback → If the keys are identical, mark waybill as not found and exit, otherwise update the stored key and continue with previous status search
[Set Previous Status Date Flag]
The system sets the search criteria to previous status waybill date → Update the waybill key feedback tracker and repeat the primary waybill system search with previous status criteria
[Access FWIQINFO Segment with B1 Key]
System accesses FWIQINFO segment with B1 key → Routing information fields are retrieved from the waybill inquiry database
[Call Waybill Inquiry System - FWIQIO]
Executing waybill inquiry system call with FWIQIO module → Call FWIQIO module using inquiry parameters and waybill root segment to retrieve equipment data
[Retrieve Additional Routing Information]
Requesting detailed routing information from inquiry system → Set inquiry segment type to 'FWIQINFO', set inquiry key to 'B1', and call inquiry system to retrieve routing details
[Parse Routing Fields into Structured Format]
Parsing routing information into individual components → If routing information is not blank then iterate through each space-separated field and extract field length by counting characters until space or end of string
[Extract SCAC Codes and Junction Points]
Extracting routing components in sequence → Set field 1 as primary SCAC code, field 2 as first junction R260 code, field 3 as secondary SCAC code, field 4 as second junction R260 code, field 5 as tertiary SCAC code, and field 6 as final junction code
[Read Container Cross-Reference]
Querying for container cross-reference information → Set inquiry segment type to 'FWIQBOTL', clear inquiry key, set function to 'GNP', and call inquiry system repeatedly until no more container cross-reference records found or maximum 30 records reached
[Retrieve Container Information from FWSWRWR]
System searches FWSWRWR database using waybill root key → Retrieve container segment information and set container status indicator
[Parse Routing Fields into Structured Format]
System processes the routing information string → Parse into structured fields including SCAC codes, junction points, and route segments up to 4 routing entries
[Access FWIQINFO Segment with Key 'B1']
The system needs to access routing information using segment key 'B1' → The FWIQINFO segment is retrieved with routing information fields populated
[Store Structured Routing Group in SHIPROOT]
Routing information storage is performed → The structured routing group containing SCAC codes and junction points is moved to the SHIPROOT routing information field
[User Authorized for Special Manifests?]
The user is not authorized for special manifests → The system should generate authorization error message 43 instead of creating the special manifest
[Create IT Export Special Manifest]
The request action is SEND → The system should generate message 23, create report line, and set IT export spawn flag for GCX101 processing
[Create TE Port Change Special Manifest]
The request action is SEND and cargo location does not match crossing port → The system should generate message 20, create report line, and set port change spawn flag for GCX101 processing
[Create TR Detour Special Manifest]
The request action is SEND and cargo has release status → The system should generate message 23, create report line, and set detour spawn flag for GCX101 processing
[Create US-US Detour Special Manifest]
The request action is SEND and waybill found with no cargo for US origin and destination → The system should generate message 23, create report line, and set US-US detour spawn flag for GCX101 processing
[Create 88-TR Export Special Manifest]
The request action is SEND and cargo is export type with no special manifest flag → The system should generate message 23, create report line, and set 88-TR detour spawn flag for GCX101 processing
[Generate Report-Only Message]
The request action is REPORT instead of SEND → The system should generate appropriate report messages (18, 19, 24, 50) without creating special manifests
[Set Security Byte to High Values]
The system configures security settings for the log message → The GCX105-SECURITY-BYTE is set to HIGH-VALUES
[Set Record Type to US Cargo]
The system sets the record type for the log message → The GCX105-US-CARGO flag is set to TRUE to indicate US cargo logging
[Set Action Code to ZZZ]
The system assigns an action code to the log message → The GCX105-ACTION-CODE is set to 'ZZZ'
[Set Log Message Text]
The system sets the log message text → The GCX105-MESSAGE is populated with CAR-ADDED-LOG-MESSAGE
[Move Log Data to Message Structure]
The system prepares the final message structure → The GCX105-INPUT is moved to GCT1051E-MSG
[Send Log Message to Alt PCB]
The system sends the log message → CIMS is called with CHNG function using ALT-PCB and GCT1051E structure
[Write Log Message to System]
The system writes the log message → WRITMSGL is called with ALT-PCB, message code, message content, message length, and module name
[Purge Message from Queue]
The system purges the message from queue → CIMS is called with PURG function using ALT-PCB to clear the message
[Move Station Segment Data to Working Storage]
The system processes the retrieved station data → The station segment data is moved to the working storage area
[Extract US Station Code]
The system extracts station identification information → The US station code is extracted from the station record
[Extract Station Name]
The system processes station information → The station name is extracted from the station record

Structural Validations

[2:User Security Validation]
The user's SCAC access is invalid AND the request is not an AEI train send request → Generate error message 14 (access denied) and set user access flag to NO
[3:Train Origin Validation]
The train origin field is blank or spaces → Generate error message 2 (missing train origin) and exit validation
[3:Train Origin Validation]
The origin is not found in station code table:
the US station code is blank
→ Generate error message 2 (invalid train origin)
[4:Estimated Time of Arrival Validation]
The ETA date equals '000000' → Generate error message 3 (invalid ETA date) and exit validation
[4:Estimated Time of Arrival Validation]
The date conversion fails:
ETA time is not numeric
hour is not 00-23
minute is not 00-59
→ Generate error message 3 (invalid ETA format)
[4:Estimated Time of Arrival Validation]
For 'S' authorization: ETA is not within 30 days before to 5 days after current date:
For other users: ETA is not within 2 days before to 2 days after current date
→ Generate error message 4 (for 'S' users) or message 21 (for other users)
[5:US Customs Train ID Generation]
A train record with the same US customs train ID already exists AND is not marked as deleted → Generate error message 6 (duplicate train ID)
[6:MERLIN Customs ID Validation]
The station's public MERLIN ID is blank:
the MERLIN ID is not found in MERLIN database
→ Generate error message 7 (missing MERLIN ID) or message 8 (MERLIN ID not found)
[47:Equipment Limit Validation]
The first equipment item is marked as 'no more equipment':
the 500th equipment item is not marked as 'no more equipment'
→ Generate error message 5 (invalid equipment list size)
[13:Equipment Type Validation]
Equipment type lookup fails → Generate error message 35 (for containers) or message 36 (for cars) and set equipment error flag
[17:Cargo Status Validation]
Cargo status is pending, deleted, or error → Generate error message 16 (cargo status invalid)
[20:Mexico Customs Documentation Check]
FEN reference number is not found → Generate error message 46, when KCM reference number is not found, generate error message 47, when cargo has hold border status, generate message 48, when cargo has DSP hold flag, generate message 49, when both hold border and DSP hold exist, generate message 52
[42:Error Message Processing]
Processing message → Increment appropriate counter (error, warning, info), track special message types (DSP holds), and handle spawn message indicators
[Equipment Format Valid?]
The equipment formatter GCCCARFM is called to validate the format → If format is invalid, equipment error message 34 is generated and processing continues to next equipment
[Generate Error Messages]
If processing results against business rules → Appropriate error messages are generated for conditions like missing waybills, cargo status issues, bond type mismatches, or regulatory violations
[Empty Equipment with Country Codes CAMX/MXCA?]
The origin-destination country codes are NOT 'CAMX' or 'MXCA' → Generate message 27 (empty equipment warning)
[Waybill Not Found Scenarios?]
Waybill is not found:
waybill is not found and container is not found
→ Generate message 10 (waybill not found error)
[Waybill Found but No Cargo?]
Container is not found:
container is found but load/empty indicator is 'L'
→ Generate message 15 (no cargo found error) with waybill root key and date
[Cargo Status Issues?]
Cargo status is pending (88-GCUSRT-RT10-CPCARGO-PENDING):
deleted (88-GCUSRT-RT10-CPCARGO-DELETED)
error (88-GCUSRT-RT10-CPCARGO-ERROR)
→ Generate message 16 (cargo status error)
[TR Bond Export Status?]
Cargo status description equals export status constant → Generate message 12 (TR bond status error)
[MT Bond Vessel Issues?]
The crossing port station code equals the cargo location ID → Generate message 25 (MT bond vessel error)
[TE Bond Vessel Issues?]
Vessel name character 23 is 'T' → Generate message 17 (TE bond vessel error)
[Non-Train Vessel Issues?]
Vessel name is not 'TRAIN' → Generate message 17 (non-train vessel error)
[Laredo Station Specific Checks?]
The crossing port is Laredo TX station → Evaluate cargo hold status and border conditions to generate messages 46-52 (FEN not found, KCM not found, hold border, hold apply, hold border apply)
[Generate Authorization Error MSG-43]
The system detects user is not authorized for special manifests (WS-USER-NOT-AUTH-4-SPCL-MANIF is true) → Generate authorization error message MSG-43 and add it to the report without creating special manifest
[SCAC Access Valid?]
The SCAC access validation returns invalid AND the request is not an AEI train send request → The system should set message fourteen as active, Execute report index increment, set user access to denied, and terminate security validation
[SCAC Access Valid?]
The system calls GCCSCAC to validate SCAC access and the validation returns SCAC-ACCESS-INVALID flag and the request is not an AEI train send request → The system sets user access to denied, generates error message fourteen, and prevents further processing
[Generate Security Error Message]
The system generates validation error messages → Message 14 is set to true and the report index is incremented
[Generate Authorization Error]
The system generates authorization error messages → Message 13 is set to true and the report index is incremented
[SCAC Access Valid?]
The system validates SCAC access permissions AND the request is not an AEI request type AND SCAC access is invalid → Set user access denied flag and generate access denied message
[Is Train Origin Empty?]
The train origin field is empty or contains only spaces → The system should set error message 2 indicating origin is required and mark validation as failed
[Station Found in Table?]
The station lookup operation completes → If the station is not found in the reference table, the system should set error message 2 for invalid origin station
[US Station Code Valid?]
The system validates the US station code → If the US station code is empty or contains only spaces, the system should set error message 2 for invalid origin station
[ETA Date = '000000'?]
The ETA date field equals '000000' → Set error message indicating ETA date is required and exit validation
[Date/Time Format Valid?]
Date conversion service validates the format:
time is not numeric
hour is not between 00-23
minute is not between 00-59
→ Set error message indicating invalid ETA format
[ETA Within Acceptable Range?]
The ETA date is less than the low date:
greater than the high date of the acceptable range
→ Set appropriate error message based on user type - message 4 for supervisor users or message 21 for regular users
[Generate Error - Duplicate Train ID]
The system attempts to create a new train record → The system generates error message 6 indicating a duplicate train identifier and prevents record creation
[Generate Error - Duplicate Train ID]
An attempt is made to create a new train with the same identifier → An error message (MSG-SIX) is generated indicating the train ID already exists
[Generate Duplicate Train ID Error]
The system attempts to create a new train with the same identifier → The system generates error message 6 indicating a duplicate train ID conflict and prevents the creation of the new record
[Administration Table Found?]
The system checks if the administration table was successfully retrieved → If table not found, generate error message 7 indicating MERLIN configuration unavailable, otherwise proceed to extract MERLIN ID
[MERLIN ID Present?]
The system checks if the MERLIN ID field contains spaces or is empty → If MERLIN ID is spaces, generate error message 7 indicating missing MERLIN configuration, otherwise proceed to database validation
[MERLIN ID Valid in Database?]
If the database query results for MERLIN ID existence → If MERLIN ID not found in database, generate error message 8 indicating invalid MERLIN ID, otherwise validation is successful
[Add Equipment Error Message]
The system handles the format error → The system must move REQ-EQP-ID to RPT-CAR-ID and REQ-LE-IND to RPT-LE-IND at the current report index
[Set Container Error Message 35]
The system determines the equipment is a container type → Error message 35 is set for the container format validation failure
[Set Car Error Message 36]
The system determines the equipment is a car type → Error message 36 is set for the car format validation failure
[TR Bond Created for IT?]
TR bond validation occurs → If TR bond was created for IT cargo but TR bond not found during processing, generate message 22 warning and add to report
[TE Bond Created for TE?]
TE bond validation occurs → If TE bond was created for TE cargo but TE bond not found during processing, generate message 32 warning and add to report
[Special IT Manifest Found?]
Special manifest validation occurs → If special IT manifest found but corresponding TE manifest location not found, generate message 45 warning and add to report
[US-MX Export Found?]
Export manifest validation occurs → If US-MX export type 88 found but TR manifest location not found, generate message 51 warning and add to report
[Add Equipment Not Found Error]
Error message generation occurs → Add message 10 (waybill not found) or message 11 (container not found) to report based on equipment type
[Generate Authorization Error Message]
Action is SEND and user is not authorized for special manifests → Generate message 43, add report line to output, and continue normal processing without creating special manifest
[Has Haulage Right Carrier?]
The system checks if the haulage right carrier field contains data → If haulage right carrier is spaces, mark as done and proceed to result processing, otherwise continue with EDI completion check
[EDI Complete Release?]
The system checks the EDI completion 418 release flag → If EDI completion 418 release equals 'Y', mark as done and proceed to result processing, otherwise check for duplicate waybill key
[EDI Complete Release = 'Y'?]
The system checks if EDI complete 418 release flag equals 'Y' → If EDI complete release is 'Y', the system accepts the waybill and terminates the loop, otherwise continues with duplicate check
[Same FWBX Key as Previous?]
The system compares the current FWBX key feedback with the previously stored FWBX key feedback → If the FWBX keys are identical, the system sets not found status and terminates the loop, otherwise updates the stored key and continues
[Set EDI Criteria - Exclude Incomplete EDI]
The system sets EDI criteria → Waybills with incomplete EDI processing are excluded from retrieval
[Haulage Right Carrier Present?]
The system checks the haulage right carrier field → If haulage right carrier is blank or spaces, the waybill is accepted, otherwise additional EDI validation is required
[EDI 418 Release Complete?]
The system checks the EDI completion status → If EDI 418 release equals 'Y', the waybill is accepted, otherwise the system continues searching for previous waybills
[Same Waybill Key as Previous?]
The system compares the current waybill key with the previously stored feedback key → If keys match, the search is terminated as not found, otherwise the system continues with previous status search
[Haulage Right Carrier Present?]
The system checks the haulage right carrier field in the waybill → If the haulage right carrier field contains spaces or is empty, accept the waybill for processing, otherwise Execute additional EDI completion validation
[EDI Completion Status Released?]
The system checks the EDI completion release status (EDI-COMP-418-RELEASE) → If the EDI completion status equals 'Y' (released), accept the waybill for processing, otherwise Execute waybill key comparison validation
[Same Waybill Key as Previous?]
The system compares the current waybill feedback key with the previously processed waybill feedback key → If the current waybill feedback key matches the previous waybill feedback key, set status to not found and stop processing, otherwise continue with previous waybill date processing
[Has Haulage Right Carrier?]
The system examines the haulage right carrier field in the waybill → If haulage right carrier is spaces, the system continues retrieval loop; otherwise proceeds to EDI completion check
[EDI Completion Status = 'Y'?]
The system checks the EDI completion release status → If EDI completion release equals 'Y', the system accepts the waybill; otherwise continues with duplicate key checking
[Same Waybill Key as Previous?]
The system compares the current FWBX key feedback with the previously stored key → If the keys match, the system marks as not found to exit the loop; otherwise updates the stored key and continues
[Equipment Type Valid?]
The equipment type validation call is not successful → Equipment error flag is set and appropriate error message is added to the report
[Add Error Message]
The system adds error messages to the report → Message 35 is added for container validation failure or message 36 for car validation failure
[Generate Equipment Error Message]
Validation failure is detected → Error message 35 is generated for container validation failure or error message 36 for car validation failure, equipment error flag is set, and processing continues to next equipment
[Validate Cargo Status Codes]
The system checks cargo status codes for pending, deleted, or error conditions → The system should generate appropriate error messages (message 16) if cargo is in pending, deleted, or error status
[Process FEN Reference Numbers]
The system searches for FEN and KCM reference number qualifiers in the segment data → The system should set FEN found flag if FEN qualifier exists with non-blank reference number, and KCM found flag if KCM qualifier exists with non-blank reference number
[Check Segment 08 Data for Hazmat]
System checks for Segment 08 data availability → System sets hazmat flag to Yes if Segment 08 data is found, otherwise sets hazmat flag to No
[Generate Empty Residue Error Message]
System processes waybill found with no cargo found condition → System generates message 44 with waybill root key and date information
[SHIPCOMM Retrieved Successfully?]
Database status code is evaluated → If retrieval successful, use retrieved data; if failed, initialize SHIPCOMM to spaces to prevent processing errors
[Generate Error Message - Threshold Exceeded]
Residue weight compliance status indicates threshold violation → Generate appropriate error message for residue weight threshold non-compliance
[Generate Container Type Error Message MSG-35]
Equipment type validation service call fails → Error message MSG-35 is generated indicating container type validation failure
[Generate Car Type Error Message MSG-36]
Equipment type validation service call fails → Error message MSG-36 is generated indicating car type validation failure
[Set Equipment Error Flag]
Error messages have been generated → Equipment error flag is set to prevent continued processing of invalid equipment
[Segment 07 Data Available?]
Segment 07 data exists and is not blank or low-values → Process the segment 07 data for cargo description extraction
[Validate Vessel Name]
The system validates MT bond requirements → Generate error message 25 for invalid MT bond vessel configuration
[Validate Vessel Name]
The system validates TE bond requirements → Generate error message 17 for invalid TE bond vessel name
[Validate Vessel Name]
The system validates bond vessel requirements → Generate error message 17 for invalid vessel name configuration
[Generate Authorization Error Message]
User is not authorized for special manifests (WS-USER-NOT-AUTH-4-SPCL-MANIF is true) → Generate message 43 (authorization error) and add equipment line to report without creating special manifest
[Generate Error Message 43 - Not Authorized]
The system processes the authorization decision → The system generates error message 43 indicating the user is not authorized for special manifest creation
[Generate Message 43 - Not Authorized Error]
The system validates user permissions → Message 43 is generated indicating user is not authorized for special manifest creation and processing continues without manifest creation
[Generate Authorization Error Message]
The system processes IT bond cargo that requires special manifest creation or processes TE bond cargo requiring port change or processes TR/default bond cargo requiring detour processing → Generate error message 43 indicating user is not authorized for special manifest operations and add the message to the report
[Is Cargo Pending?]
The cargo status is pending, deleted, or in error state → Generate cargo status error message and halt processing for this cargo
[Is DSP Hold Applied?]
DSP hold is applied to the cargo → Generate DSP hold warning message
[Is FEN Documentation Missing?]
FEN reference number qualifier is not found in the segment data → Generate FEN missing warning message
[Is KCM Documentation Missing?]
KCM reference number qualifier is not found in the segment data → Generate KCM missing warning message
[Generate Error Message - Missing Waybill for Loaded Equipment]
The equipment is marked as loaded AND no waybill is found AND the equipment is not an SBU Van unit → Generate error message MSG-TEN indicating missing waybill for loaded equipment
[Generate Error Message - Missing Cargo for Loaded Equipment]
No cargo records are found for the equipment AND the equipment is marked as loaded AND the equipment is not a conveying car AND the equipment is not an idler car → Generate error message MSG-FIFTEEN indicating missing cargo records for loaded equipment with waybill and date information
[Is Segment 02 Data Found?]
The system checks for segment 02 reference data availability → If segment 02 data is not found or empty, skip Mexico customs documentation validation
[Is FEN Documentation Missing?]
The system validates FEN documentation presence → If FEN documentation is not found, generate message 46 for missing FEN documentation
[Is KCM Documentation Missing?]
The system validates KCM documentation presence → If KCM documentation is not found, generate message 47 for missing KCM documentation
[Border Clearance: Release Status Check]
The system checks cargo release status → If status equals release, proceed with border clearance detour, if invalid status generate message 31, otherwise skip
[Generate Empty Equipment Error Message]
The cargo is found and marked as empty equipment → Error message 27 (empty equipment message) should be generated
[Generate Authorization Error Message]
The user is not authorized for special manifest creation → Generate message forty-three, add the report line to output, and exit port change processing
[Generate Error Message 43]
The system attempts to create a special manifest → Generate error message 43 for user not authorized for special manifests and add to report output
[Generate Message 31 - Invalid Cargo Status]
The system validates cargo status for border clearance → Generate message 31 indicating invalid cargo status and add to report output
[Generate Error Message 43: User Not Authorized for Special Manifests]
The system processes the unauthorized special manifest request → The system should generate error message 43 indicating the user is not authorized for special manifests
[Generate Error Message 31 - Invalid Status]
Cargo status is invalid for US-Mexico export processing → Generate error message 31 indicating invalid cargo status
[Generate Container Not Found Error]
Both FWSWRWR and FWIQ inquiry systems return no container information → Error message 11 is generated indicating container not found
[Convert Error 43 to Warning 18]
The system processes error message classification → Convert message type 43 to message type 18, increase warning count by 1, and decrease error count by 1
[Message Type = Error?]
If the message type indicator → If the message type is error, the system proceeds to error-specific processing and counter increments
[Is Error Type 43?]
The system checks the specific error type indicator → If the error type is 43, the system increments the error type 43 counter in addition to the general error counter
[Increment Error Type 43 Counter]
The system processes the error classification → The system increments the error type 43 counter by 1
[Increment General Error Counter]
The system processes the error classification → The system increments the general error counter by 1
[Check Error 43 Count vs Total Errors]
The system compares the error type 43 count against the total error count → If the error type 43 count equals the total error count, the system proceeds with error-to-warning conversion
[Convert Error 43 to Warning Type 18]
The system performs error-to-warning conversion → The system changes all error type 43 messages to warning type 18
[Adjust Error Counter Down]
The system adjusts the counters for the conversion → The system decrements the error counter by 1 for each converted message
[Classify as Error Message]
The message type indicator shows it is an error message → The system increments the error count by one
[Check Error Type 43?]
The message type indicator equals 43 → The system increments the special error type 43 counter by one
[Classify as Warning Message]
The message type indicator shows it is a warning message → The system increments the warning count by one
[Check Warning Types 49/52?]
The message type indicator equals 49 or 52 → The system increments the DSP count by one
[Classify as Information Message]
The message type indicator shows it is an information message → The system increments the information count by one
[Set Overflow Message]
An attempt is made to add another entry beyond the limit → The system sets message type 9 as an overflow indicator
[Add Spawn Count to Error Count]
The system calculates the total error count for display → The spawn count is added to the existing error count to show total issues
[Convert Error Messages to Warning Messages]
The system processes error messages for final reporting → Specific error messages (type 43) are converted to warning messages if error count matches type 43 count
[Validate Module Parameters]
The module execution completes → The system must validate that the module parameters were valid and the transmission was successful, otherwise terminate with system error
[Verify Email Send Success]
The system checks the email transmission result → If the email return status is not successful, the system must handle the email send failure
[Email Content Exceeds Line Limit?]
The system checks if the current line count exceeds 699 lines → The system determines whether to split the email into multiple batches or send as a single transmission
[Email Transmission Successful?]
The system checks the email return status flag → The system determines if the transmission was successful based on the return status
[Retry Successful?]
The system checks the retry transmission status → If retry fails, the system generates an error message 'SEND TO FILE OF OM01247 FAILED' and abends the process
[Check Line Count > 699?]
The line count reaches or exceeds 699 lines → The current batch must be transmitted immediately and a new batch started
[Set Error Recipients]
The system handles transmission failure → TO usercode is cleared, error recipient 'AEI9999' is set as first recipient, and 'OM01247' is set as second recipient
[Call EMCSEND3 for Error Notification]
The system calls EMCSEND3 for error notification → Error notification email is transmitted to designated error recipients with same message content and formatting parameters
[Error Notification Successful?]
The error notification transmission status is evaluated → If error notification succeeds, clear message buffer and continue; if error notification fails, trigger system abend with 'SEND TO FILE OF OM01247 FAILED' message
[Line Count > 699?]
The system checks the current line count → The system shall trigger email transmission if the line count exceeds 699 lines
[Send Error Notification to Support]
Error notification is sent to support → The system shall set AEI9999 as the first recipient, OM01247 as the second recipient, and attempt to send the error notification
[Line Count > 699?]
The line subscription counter is evaluated → If the line counter exceeds 699 lines, trigger email batch sending process
[Send Error Notification to Support]
Error notification needs to be sent → Call EMCSEND3 to send error notification to support recipients AND if this also fails, generate system abend with message 'SEND TO FILE OF OM01247 FAILED'
[Handle Email Send Errors]
The email send operation returns an unsuccessful status → An error notification is sent to AEI9999 and OM01247 support addresses, and if that also fails, the system abends with an error message
[Email Size Limit Reached?]
The line counter exceeds 699 lines → Trigger immediate email send and prepare for continuation email
[Send Error Notification to Support]
The EMCSEND3 return status indicates failure → Clear recipient addresses, set error notification recipients to AEI9999 and OM01247, and attempt to send error notification
[Check Equipment Type]
The origin-destination country codes are not 'CAMX' or 'MXCA' → Generate message twenty-seven indicating empty equipment issue
[Generate Equipment Type Error]
Equipment is not a unit SBU van → Generate message ten indicating waybill not found
[Generate Equipment Type Error]
Processing waybill validation → Generate message twenty-six indicating waybill processing error
[Generate Cargo Status Error]
Processing cargo validation → Generate message fifteen with waybill root key and date
[Generate Load Status Warning]
Idler indicator is not 'I' → Generate message forty-four with waybill root key and date
[Generate Documentation Warning]
Equipment is not conveying car and idler indicator is not 'I' → Generate message fifteen with waybill root key and date
[Generate Cargo Status Error]
Status is pending, deleted, or error → Generate message sixteen indicating invalid cargo status
[Generate Bond Type Error]
Cargo status description equals export status → Generate message twelve indicating TR bond export issue
[Generate Bond Type Error]
Station code matches cargo location ID → Generate message twenty-five indicating MT bond location issue
[Generate Bond Type Error]
Vessel name character at position 23 is 'T' → Generate message seventeen indicating invalid vessel name
[Generate Bond Type Error]
Vessel name is not 'TRAIN' → Generate message seventeen indicating invalid vessel name
[Generate Port Requirement Error]
DSP hold status is yes → Generate message fifty-two indicating hold border with DSP hold
[Generate Port Requirement Error]
DSP hold status is yes → Generate message forty-nine indicating DSP hold
[Generate Port Requirement Error]
Cargo status description equals hold border → Generate message forty-eight indicating hold border without DSP
[Generate Documentation Warning]
FEN reference number is not found in segment data → Generate message forty-six indicating missing FEN reference
[Generate Documentation Warning]
KCM reference number is not found in segment data → Generate message forty-seven indicating missing KCM reference
[Error Message?]
The message is classified as an error message (MSG-ERR) → Increment the total error count by 1
[Is Message Line?]
The entry is evaluated for message line status → Continue with message type classification if it is a message line, otherwise skip processing
[Error Message - Add to Error Count]
The message is classified as an error type → The system increments the error count by 1
[Warning Message - Add to Warning Count]
The message is classified as a warning type → The system increments the warning count by 1
[Is Message Line Type?]
The system checks if the report entry is a message line type → If the entry is not a message line type, skip all message processing and complete classification
[Classify as Error Message]
The message severity is classified as error level → Increment the error counter by 1, and if the message type is 43, also increment the special error counter (ERR-43-CNT) by 1
[Error Message?]
The message is classified as an error message → The system increments the error counter by 1
[Type 43 Error?]
The error message type indicator equals 43 → The system increments the Type 43 error counter by 1
[Warning Message?]
The message is classified as a warning message → The system increments the warning counter by 1
[DSP Message Type 49 or 52?]
The message type indicator equals 49 or 52 → The system increments the DSP counter by 1
[Information Message?]
The message is classified as an information message → The system increments the information counter by 1
[Increment Error Counter]
The message type is determined to be an error → The system adds 1 to the error message counter
[Set Overflow Message]
The maximum number of report lines has been reached → The system sets message type 9 as an overflow indicator
[First Equipment Entry Empty?]
The first equipment entry in the request is empty (REQ-NO-MORE-EQP(1) is true) → The system sets error message MSG-FIVE and adds it to the report index to indicate no equipment was provided
[Equipment Count > 499?]
The equipment list contains more than 499 items (NOT REQ-NO-MORE-EQP(500) is true) → The system sets error message MSG-FIVE and adds it to the report index to indicate too many equipment items were provided
[ER Weight Threshold > 7?]
The residue weight is greater than 7 units → Set ER weight threshold greater than 7 flag for subsequent error message generation
[Generate Error Message 44 - Empty Residue Threshold Exceeded]
No cargo is found for the waybill → Generate error message 44 with waybill root key and date information
[Generate Equipment Error Message]
The system processes the validation failure → If the equipment is a container, message 35 should be generated, otherwise message 36 should be generated, and the equipment error flag should be set
[Set Segment 02 Found Flag]
The system checks if segment 02 data contains spaces or low-values → If segment 02 data is spaces or low-values, set segment 02 not found flag, otherwise set segment 02 found flag
[Set Segment 07 Found Flag]
The system checks if segment 07 data contains spaces or low-values → If segment 07 data is spaces or low-values, set segment 07 not found flag, otherwise set segment 07 found flag
[Set Segment 08 Found Flag - Hazmat Indicator]
The system checks if segment 08 data contains spaces or low-values → If segment 08 data is spaces or low-values, set segment 08 not found flag indicating no hazmat, otherwise set segment 08 found flag indicating hazmat present
[Check Port Change Conditions]
Location ID1 does not match the station crossing port code → If action is REPORT, generate message 19 with station code, otherwise if action is SEND and user is not authorized for special manifest, generate error message 43, otherwise generate message 20 and set port change spawn flag
[Check Release Status]
Cargo short description equals release status → If action is REPORT, generate message 18, otherwise if action is SEND and user is not authorized for special manifest, generate error message 43, otherwise generate message 23 and set detour spawn flag
[Check Vessel Name = TRAIN]
Vessel name is not 'TRAIN' and not spaces and station crossing port code equals cargo location ID → Generate error message 25 for invalid vessel name and location combination
[Check Vessel Name]
Vessel name character at position 23 is 'T' → Generate error message 17 for invalid TE vessel name format
[Check Vessel Name]
Vessel name is not 'TRAIN' → Generate error message 17 for invalid vessel name
[Segment Retrieval Successful?]
The system checks the retrieval operation result → The system should determine if segment data was successfully retrieved based on error status being empty
[Abort - Table Overflow]
Table overflow condition is detected → System aborts with train list table overflow error message
[Abort - Insert Failed]
Insert failure condition is detected → System aborts with database insert failure error message
[SEND Action with No Errors and No Spawns?]
The request has no validation errors AND no spawn processing requirements → Execute the full transmission workflow including database storage, EDI transmission, duplicate removal, customs reporting, PDF generation, station-specific processing, acknowledgment, and audit logging
[Error Type Classification]
If the message type indicator → Messages are classified as errors (increment error counter), warnings (increment warning counter), or information (increment info counter)
[Increment Error Counter]
The system processes the error message → The report error counter is incremented by one
[Check Error Type 43]
The system checks if the message type indicator equals 43 → Type 43 errors increment a special Type 43 counter in addition to the general error counter
[Convert Error to Warning]
The system processes the count correction → Excess Type 43 error messages are converted to warning type 18 messages
[Database Insert Successful?]
Validating database insert success → If GCCUTRIO return indicates already exists error, then system abend with insert failed message, otherwise insertion is successful
[EDI Transmission Successful?]
The transmission process completes → The system must verify the transmission was successful AND if unsuccessful, trigger parameter validation error handling
[Validate Module Parameters]
Parameter validation is performed → The system must validate all module parameters AND if invalid, generate an abend condition with error message 'GCCU358T MODULE PARAMETERS INVALID'
[Any Processing Errors?]
The system checks for any processing errors in the report → If no errors exist (RPT-NO-ERROR is true), proceed to check for spawn messages, otherwise proceed to spawn message evaluation for error handling
[Add Spawn Count to Error Count]
The system calculates the total error count for reporting → Add the spawn message count to the existing error count to get the total error count
[Convert Error Messages to Warning Messages]
If message types for final classification → Convert specific error messages (type 43) to warning messages if error count matches the count of type 43 messages, otherwise keep as warnings
[Convert Error Messages to Warning Messages]
The system processes spawn-related messages for final reporting → Convert diversion spawn messages to message type 19 and IT export spawn messages to message type 18, then add spawn count to warning count
[Line Count > 699?]
The line count reaches or exceeds 699 lines → The current email batch must be sent and a new batch must be started
[Send Error Notification to Support]
The system detects email transmission failure → The system clears recipient list, sets AEI9999 and OM01247 as error recipients, and attempts to send error notification using the same email service
[Handle Email Error]
The email send operation is unsuccessful → The system terminates processing with error message 'SEND TO FILE OF OM01247 FAILED'
[Increment Error Count]
The message type is classified as an error message → The system increments the error count by 1 for report statistics
[Report Maximum Reached?]
The system checks if the report has reached its maximum capacity → If maximum capacity is reached, set an overflow message indicator, otherwise continue normal processing
[Format Error Subject Line with SQLCODE]
The system formats the error notification → The subject line should contain 'GCX003 DB2 SQLCODE:' followed by the specific SQLCODE value and the message text should contain the same error information
[Handle Database Error]
The system handles database error → The system should create detailed error message including operation type and train identifier, then terminate processing with abend
[Has Haulage Right Carrier?]
The system checks if the haulage right carrier field contains data → If haulage right carrier is blank or spaces, accept the waybill as found, otherwise Execute additional EDI completion checks
[EDI Complete Release Available?]
The system checks the EDI completion release status → If EDI completion release equals 'Y', accept the waybill as found, otherwise continue with duplicate key checking
[Generate Container Not Found Error]
System determines container cannot be found → Error message 11 is generated indicating container not found
[Routing Info Fields Available?]
The routing information fields are checked for data availability → Processing continues only if routing fields are not spaces or low-values, otherwise routing extraction is skipped
[Check if US CCN exists for logging]
The system checks if the US CCN from the added cargo list is not blank or spaces → If US CCN exists, proceed with log message creation, otherwise skip logging process
[Equipment ID is Blank or Error/Warning/Info Message?]
The equipment ID is blank or the entry contains error messages (ERR>), warning messages (WRN>), or info messages (INF>) → Skip this entry and move to the next scan position without duplicate processing
[Set Station Not Found Error]
No matching station record is found in the reference table → A station not found error is set with message code 2
[Set Invalid US Station Code Error]
The system validates the US station code content → An invalid US station code error is set with message code 2

Detailed EDI User Stories

Module: GCCTBIO 1 Consolidated Epic Story

Module: GCCUSIO 1 Consolidated Epic Story

Module: GCCADDT 1 Consolidated Epic Story

Module: GCCU358T 1 Consolidated Epic Story

Module: CCISCOM 1 Consolidated Epic Story

Module: CERR 1 Consolidated Epic Story

Module: CIMS 1 Consolidated Epic Story

Module: WRITMSGL 1 Consolidated Epic Story

Module: GCCCARFM 1 Consolidated Epic Story

Module: GCCDBL 1 Consolidated Epic Story

Module: GCCSCAC 1 Consolidated Epic Story

Module: GCCUTRIO 1 Consolidated Epic Story

Module: GCSTONLY 1 Consolidated Epic Story

Module: GCX904 1 Consolidated Epic Story

Module: GCX003 1 Consolidated Epic Story