Previous Page | Next Page

OpenVMS Operating Environment

Error Messages For OpenVMS


Given transport file is bad

For general recovery actions for this error message, see Bad Transport File.

The transport file is suspected of being corrupt.

  1. Find out whether the transport file contains a corrupting character.

    $DIR/FULL transport-file

    The output confirms that the transport file contains a corrupting character.

    Record attributes: Carriage return Carriage control

  2. Your next action will depend on the following conditions that apply to your environment:

    1. If your operating environment has the NFTCOPY (Network File Transfer Copy) command and you are moving the transport file to a DOS target computer, remove the carriage return (CC) attribute from the transport file and move the transport file again to the target computer:

      NFTCOPY/IMAGE/FIXED/CC=NONE NODE"userid password"
        ::disk:[dir] tranfile target

      Here is an example:

      NFTCOPY/IMAGE/FIXED/CC=NONE CHEX "brown bird":
       dua0[brown]tranfile c:\blue\target

    2. If your source computer is running SAS 6.08 at maintenance level TS405 or later, set the NONE value to the CC= option in the LIBNAME or FILENAME statement, whichever is appropriate.

      Note:   See the top of the SAS log for the SAS release and maintenance level.  [cautionend]

      Here is an example.
      libname grades 'file-path';
      libname tranfile xport 'file-path' cc=none;
      proc copy in=grades out=tranfile;
      run;

    3. If you are running a SAS release that precedes SAS 6.08 at maintenance level TS405, you must post-process the transport file to remove the carriage returns.

      Create a new file named REMCC.FDL to contain these entries, including CARRIAGE_CONTROL NONE.

      RECORD
      BLOCK_SPAN YES
      CARRIAGE_CONTROL NONE
      FORMAT FIXED
      SIZE 80

      Specify this DCL command to create a new file named NEWTRAN.SEQ:

      $ CONVERT/FDL=REMCC.FDL TRAN.SEQ NEWTRAN.SEQ
      $ DELETE TRAN.SEQ

      Verify that the file attributes of the new transport file do not include carriage returns:

      $ DIR/FULL NEWTRAN.SEQ

  3. At the source computer, transfer the transport file to the target computer again.

    If you are still unable to import a transport file that has the correct attributes, you can try using the reblocking program. For details, see Reblocking a Transport File.


Member or library unavailable for use in file

The transport file is suspected to be corrupt. For recovery actions, see Given transport file is bad.


Truncated record

For general recovery actions for this error message, see Truncated record.

Usually, this message is displayed when the transport file is moved to a virtual disk or a shared disk under operating environments such as DOS, Macintosh, or UNIX. Virtual disk or shared disk directories often have a record format of STREAM instead of FIXED.

To recover, perform these steps.

  1. Verify the transport file attributes by using the DIR/FULL command.

  2. To set record attributes correctly, create a new file named FIXREC.FDL file to contain these entries.

    RECORD
    BLOCK_SPAN YES
    CARRIAGE_CONTROL NONE
    FORMAT FIXED
    SIZE 80

  3. Specify this DCL command to create a new file named NEWTRAN.FDL:

    $ EXCHANGE/NETWORK/TRANSFER_MOD=BLOCK/FDL=TRAN.FDL 
     TRAN.SEQ NEWTRAN.SEQ

  4. Verify that the new transport file attributes do not include carriage returns:

    $ DIR/FULL NEWTRAN.SEQ

  5. At the source computer, transfer the transport file to the target computer again.


Internal error from getting data

The transport file is suspected to be corrupt. For recovery actions, see Truncated record.

Previous Page | Next Page | Top of Page