How to avoid the "INVALID ASM2 PREFIX DEFINED IN $OPTIONS - return code 16" error message on duplexing job?.

Document ID:  TEC494024
Last Modified Date:  06/07/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA ASM2 Backup and Restore
  • CA RSVP

Releases

  • CA ASM2 Backup and Restore:Release:4.2

Components

  • CA ASM2 Backup and Restore:ASM2
Summary:

ASM2 has a specific requirement for naming of LOXXX files. File names that don't meet the standard will cause an invalid prefix error message.

Instructions:

The LOXXX file must be named prefix.BKUP.* or prefix.ARCH.*.

The prefix for the LOXXX file is specified in the $OPTIONS file with the $PREFIX parm. When looking for the LOXXX file, ASM2 looks for the next token after the prefix to be either ARCH or BKUP. Anything else in that position will cause an invalid prefix error. Additional tokens may be added after ARCH or BKUP.

For example:

$OPTIONS has:

  $PREFIX MY.ASM2.PRODLIB 

Valid names would include:

  MY.ASM2.PRODLIB.BKUP.LOUSER 
  MY.ASM2.PRODLIB.BKUP.DSA.XYZ.LOUSERA 
  MY.ASM2.PRODLIB.ARCH.OLD.LOUSERB 

 

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >