This appendix describes the Pioneer and Voyager LONG_FDTNAME=Y Processing. The Pioneer and/or Voyager agent, after receiving a TSS LIST request as a part of its internal logic, issues a TSS LIST for appropriate Top-Secret ACID.
When the list request is issued, Pioneer and/or Voyager will issue a @PSCRCHUSR acid dsn for Pioneer or @VSRCHUSR acid dsn through module IDFISCMD to IBM's System Rexx.
The new module uses MGCRE macro to issue this request. AXR (System Rexx) queues up the request and searches its REXXLIBs for the Rexx clist. The clists perform a TSO "LISTDS" for the dsname that is passed to System Rexx. If the dataset is found it is deleted.
A TSS LIST for the acid is then performed and the dsn is built. During this period, Pioneer and or Voyager will wait until it can allocate the dataset as OLD. When able to allocate Pioneer and/or Voyager will build messages for the LDAP, convert to ASCII, encrypt them and then issue a write socket.
The DSN specified must be unique for Pioneer and Voyager. The AXR STC (Started Task) must be able to update and delete these datasets.
Specify the control parameter LONG_FTDNAMES=Y when DSN=<YOURHLQ.DATASERNAME>. The YOURHLQ.DATASERNAME must be unique for each STC. If this feature is not required, code the control parameter LONG_FTDNAMES=N. LONG_FDT=Y indicates that the connector will support user-defined fields greater than 255 bytes.
They are also preallocated by the PSRCHUSR and VSRCHUSR Rexx clists in the REXXlib specified for System Rexx.