BS2000 Agent: BS2-Tar Utility Fails to Start with PROGRAM INTERRUPT (EC=48, CODE=NRT0200)
search cancel

BS2000 Agent: BS2-Tar Utility Fails to Start with PROGRAM INTERRUPT (EC=48, CODE=NRT0200)

book

Article ID: 410513

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

When attempting to start the bs2-tar program on a BS2000 system, typically as part of or in preparation for Automic BS2000 Agent setup, the program terminates abnormally with a PROGRAM INTERRUPT error and initiates a system dump.

Symptoms (Console Output):
The BS2000 console displays messages similar to:

% 185-000.110515 % IDA0N64 SNAP INITIATED BY CDUMP
% 185-000.110515 % IDA0N51 PROGRAM INTERRUPT AT LOCATION 'FE08D59C(PBLPHAS+023CC), EC=48, CODE=NRT0200'
...
% 185-000.110713 % EXC0736 ABNORMAL TASK TERMINATION. ERROR CODE 'NRT0200': /HELP-MSG NRT0200

Environment

Product: CA Automic Workload Automation
Component: BS2000 Agent, bs2-tar utility
OS: BS2000

Cause

The PROGRAM INTERRUPT (specifically EC=48, indicating an Addressing Exception) and CODE=NRT0200 occur because the bs2-tar executable file was corrupted during transfer to the BS2000 system.

The primary cause of corruption is typically using text (ASCII) mode FTP transfer instead of binary mode. Executable files, libraries, and compressed archives must be transferred in binary mode to preserve their integrity. Transferring them in text mode can alter bytes (e.g., newline character conversions) which renders the program unusable and leads to memory access violations upon execution.

The tool OpenFT is not usable to transfer the bs2-tar.bin file. Even if the binary mode of OpenFT is selected the file transfer will not be transparent so the file arrives corrupt on the BS2000 system.

Resolution

To resolve this issue, ensure the bs2-tar utility (and any other executable or binary files) is transferred to the BS2000 system using a method that guarantees binary integrity.

Steps:

  1. Delete any previously transferred and corrupted versions of the bs2-tar executable on the BS2000 system.
  2. Use a standard FTP client connecting to an FTP server configured directly on the BS2000 system.
    • Ensure your FTP client is configured for Binary mode for the transfer. (This is often a setting in the FTP client itself, or by using the binary command after connecting via CLI FTP).
    • Transfer the bs2-tar file from your source (e.g., Automic Agent installation package) to the BS2000 system via FTP in binary mode.
  3. Once transferred, unpack/catalog the bs2-tar file on BS2000 using the appropriate BS2000 commands as per the official Automic documentation (e.g., /cat for PAM files, or ARCHIVE utility if it's an archive) and Attempt to start the bs2-tar program again. It should now execute without the PROGRAM INTERRUPT error.

Additional Information

  • Always refer to the official Automic documentation for the precise installation and transfer instructions for BS2000 components.
  • EC=48 (Addressing Exception) is a low-level BS2000 error indicating an attempt to access an invalid memory address, typically caused by a corrupted executable or a software bug.
  • The NRT0200 message can provide more specific context if /HELP-MSG NRT0200 is executed on the BS2000 console.
Powered by Wolken Software