HP 3000 Manuals

(S/R) (Continued) [ MPE/iX Error Messages Manual Volume II ] MPE/iX 5.5 Documentation


MPE/iX Error Messages Manual Volume II

(S/R) (Continued) 

------------------------------------------------------------

970          MESSAGE    WARNING: 'NOHFSWARN' OPTION IS NO LONGER
                      SUPPORTED.  PLEASE REMOVE THIS OPTION FROM BACKUP
                      PROCEDURES.  OPTION IGNORED. (S/R 970)

           CAUSE      You are specifying the NOHFSWARN option to store.
                      This option is no longer supported or needed.

           ACTION     Remove the NOHFSWARN option from any STORE job
                      streams.

-------------------------------------------------------------

971          MESSAGE    'TRANSPORT' OPTION CANNOT BE USED WITH THE
                      'TRANSPORT=MPEXL' OPTION. (S/R 971)

           CAUSE      TRANSPORT and TRANSPORT=MPEXL options are not
                      allowed on the same command line.

           ACTION     Delete one of the options and retype the command.

-------------------------------------------------------------

972          MESSAGE    'TRANSPORT=MPEXL' OPTION CANNOT BE USED WITH THE
                      'TRANSPORT' OPTION. (S/R 972)

           CAUSE      TRANSPORT=MPEXL and TRANSPORT options are not
                      allowed on the same command line.

           ACTION     Delete one of the options and retype the command.

-------------------------------------------------------------

973          MESSAGE    WARNING: 'TRANSPORT=MPEXL' OPTION HAS BEEN
                      REDUNDANDLY SPECIFIED (S/R 973)

           CAUSE      You have entered TRANSPORT=MPEXL twice.

           ACTION     Information only, no action required.

-------------------------------------------------------------

974          MESSAGE    'NOHFSWARN' OPTION CANNOT BE USED WITH THE
                      'HFSWARN' OPTION (S/R 974)

           CAUSE      The NOHFSWARN and HFSWARN options cannot be used
                      together.  However, neither option is supported any
                      more.

           ACTION     Remove any NOHFSWARN or HFSWARN options from your
                      STORE commands.

-------------------------------------------------------------

976          MESSAGE    EXPECTED 'onlineparm[,onlineparm..]' AFTER
                      'ONLINE=' option where   ''onlineparm IS 'START' OR
                      'END', OPTIONALLY BE FOLLOWED BY time (hh:mm:ss) or
                      A SK (S/R 976)''

           CAUSE      'ONLINE =' option must be followed by START or END
                      options.  \ACTIO N\ Check your command line and
                      specify START or END for 'ONLINE=' option.

-------------------------------------------------------------

977          MESSAGE    'ONLINE=END' OPTION CANNOT BE USED WITH 'ONLINE'
                      OPTION (S/R 977)

           CAUSE      You cannot specify both ONLINE and ONLINE=END.

           ACTION     Decide what type of online backup you want to
                      perform, then specify either ONLINE or ONLINE=END.

-------------------------------------------------------------

978          MESSAGE    'ONLINE=END' OPTION CANNOT BE USED WITH
                      'ONLINE=START' OPTION (S/ R 978)

           CAUSE      You cannot specify both START and END sync points.

           ACTION     Remove one of the ONLINE options and re-run the
                      command.

-------------------------------------------------------------

979          MESSAGE    WARNING: 'ONLINE=END' OPTION HAS BEEN REDUNDANTLY
                      SPECIFIED (S/R 979)

           CAUSE      You have specified the ONLINE=END option more than
                      once.

           ACTION     Information only.

-------------------------------------------------------------

980          MESSAGE    'ONLINE=START' OPTION CANNOT BE USED WITH
                      'ONLINE' OPTION (S/R 98 0)

           CAUSE      You cannot use the ONLINE option with the
                      ONLINE=START option.

           ACTION     Remove one of the ONLINE options and re-run the
                      command.

-------------------------------------------------------------

981          MESSAGE    WARNING: 'ONLINE=START' OPTION HAS BEEN
                      REDUNDANTLY SPECIFIED (S/ R 981)

           CAUSE      You have specified the ONLINE=START option more
                      than once.

           ACTION     Information only.

-------------------------------------------------------------

982          MESSAGE    SYNC TIME MUST BE USED WITH 'START' OR 'END'
                      PARAMETERS (S/R 982)

           CAUSE      You must specify ONLINE=START or ONLINE=END if you
                      specify a time parameter to ONLINE.

           ACTION     Either remove the time specification or add START
                      or END to the ONLINE option.

-------------------------------------------------------------

983          MESSAGE    'ONLINE=time' OPTION CANNOT BE USED WITH 'ONLINE'
                      OPTION (S/R 983 )

           CAUSE      You cannot specify ONLINE=time and ONLINE in the
                      same command.

           ACTION     Remove one of the ONLINE options and re-run the
                      command.

-------------------------------------------------------------

984          MESSAGE    MULTIPLE SYNC TIMES CAN NOT BE SPECIFIED (S/R
                      984)

           CAUSE      Only one time can be specified for the online sync
                      point.

           ACTION     Remove all but one of the times and re-run the
                      command.

-------------------------------------------------------------

985          MESSAGE    INVALID TIME SPECIFIED, MUST BE SPECIFIED AS
                      HH:MM[:SS] (e.g. 14:  30:30) (S/R 985)

           CAUSE      You specified the online sync time incorrectly.

           ACTION     Specify the time as HH:MM[:SS] and re-run the
                      command.

-------------------------------------------------------------

986          MESSAGE    'STOREDIRECTORY' OPTION CANNOT BE USED WITH
                      'TRANSPORT' TO MPEv.  (S/R 986)

           CAUSE      The STOREDIRECTORY option cannot be used to create
                      MPEv media.

           ACTION     Delete one of the two options and re-run the
                      command.

-------------------------------------------------------------

987          MESSAGE    'STOREDIRECTORY' OPTION CANNOT BE USED WITH
                      'NOSTOREDIRECTORY' OP TION (S/R 987)

           CAUSE      You cannot specify both STOREDIRECTORY and
                      NOSTOREDIRECTORY.

           ACTION     Remove one of the options and re-run the command.

-------------------------------------------------------------

988          MESSAGE    WARNING: 'STOREDIRECTORY' OPTION HAS BEEN
                      REDUNDANTLY SPECIFIED ( S/R 988)

           CAUSE      You have specified the STOREDIRECTORY option more
                      than once.

           ACTION     Information only.

-------------------------------------------------------------

989          MESSAGE    EXPECTED '=directoryname' AFTER 'STOREDIRECTORY'
                      OPTION. SYNTAX ' STOREDIR[ECTORY]=directoryname'
                      (S/R 989)

           CAUSE      No filename was specified after the STOREDIRECTORY
                      option.

           ACTION     Specify a valid MPE or HFS-style file name of the
                      file that contains the store disk directory for
                      this backup and re-run the command.

-------------------------------------------------------------

990          MESSAGE    INVALID FILENAME FOR STOREDIRECTORY (S/R 990)

           CAUSE      An invalid name was specified for the
                      STOREDIRECTORY option.

           ACTION     Specify a valid MPE or HFS filename.

-------------------------------------------------------------

991          MESSAGE    'LOGVOLSET' OPTION CANNOT BE USED WITH
                      'TRANSPORT' TO MPEv. (S/R 991)

           CAUSE      The LOGVOLSET option cannot be used to create MPEv
                      media.

           ACTION     Remove one of the options and re-run the command.

-------------------------------------------------------------

992          MESSAGE    WARNING: 'LOGVOLSET' OPTION HAS BEEN REDUNDANTLY
                      SPECIFIED (S/R 9 92)

           CAUSE      The LOGVOLSET option was specified more than once.

           ACTION     Information only.

-------------------------------------------------------------

993          MESSAGE    EXPECTED '=volumesetname' AFTER 'LOGVOLSET'
                      OPTION. SYNTAX 'LOGVO LSET=volumesetname'  (S/R
                      993)

           CAUSE      The name of a valid volume set was not specified
                      after the LOGVOLSET option.

           ACTION     Check your command line and specify a valid volume
                      set for the LOGVOLSET option.

-------------------------------------------------------------

994          MESSAGE    'NOSTOREDIRECTORY' OPTION CANNOT BE USED WITH
                      'TRANSPORT' TO MPEv . (S/R 994)

           CAUSE      The NOSTOREDIRECTORY option cannot be used to
                      create MPEv media.

           ACTION     Remove one of the options and re-run the command.

-------------------------------------------------------------

998          MESSAGE    STORE DIRECTORY FILENAMES MAY NOT BE HFS
                      DIRECTORIES  (S/R 998)

           CAUSE      The file specified for the STOREDIRECTORY option
                      was an HFS directory.

           ACTION     Specify a non-HFS directory filename for the
                      STOREDIRECTORY option.

-------------------------------------------------------------

999          MESSAGE    INDIRECT FILENAMES MAY NOT BE HFS DIRECTORIES
                      (S/R 999)

           CAUSE      An HFS directory was specified as an indirect file.

           ACTION     Specify a non-HFS directory file for a STORE
                      indirect file.

-------------------------------------------------------------

1000         MESSAGE    STORE DIRECTORY FILENAMES MAY NOT BE WILDCARDED
                      (S/R 1000)

           CAUSE      A wildcard was specified as an indirect file.

           ACTION     Specify one indirect file at a time on the STORE
                      command line.

-------------------------------------------------------------

1001         MESSAGE    INDIRECT FILENAMES MAY NOT BE WILDCARDED.  (S/R
                      1001)

           CAUSE      You cannot include wildcard characters in the
                      indirect filename.

           ACTION     Retype the command and enter a valid filename.

-------------------------------------------------------------

1002         MESSAGE    FILE NAME PART LENGTH TOO LONG.  A WILDCARDED
                      NAME PART CANNOT EXCEED 8 LOGICAL CHARACTERS, WHERE
                      A LOGICAL CHARACTER IS ONE OF @, #, ?, a-z, 0-9, OR
                      A CHARACTER SET '[]'  (S/R 1002)

           CAUSE      You included an invalid filename.

           ACTION     Retype the command and enter a valid filename.

-------------------------------------------------------------

1003         MESSAGE    FILE NAME PART LENGTH TOO LONG.  A NAME PART
                      CANNOT EXCEED 8 CHARACTERS IN LENGTH  (S/R 1003)

           CAUSE      Same as message content.

           ACTION     Retype the command and include a valid file name.

-------------------------------------------------------------

1004         MESSAGE    EXPECTED A ',' OR ';' TO DELIMIT A FILESET.
                      FILESET NAMES MAY BE COMPOSED OF A MAXIMUM OF THREE
                      PARTS, FILENAME.GROUPNAME.ACCOUNTNAME.  (S/R 1004)

           CAUSE      You did not include a comma or semicolon.

           ACTION     Check the syntax and retype the command.

-------------------------------------------------------------

1005         MESSAGE    NEGATIVE FILESETS (FILE EXCLUSION) CANNOT BE USED
                      WITH INDIRECT FILES.  (S/R 1005)

           CAUSE      Same as message content.

           ACTION     Retype the command with valid files.

-------------------------------------------------------------

1007         MESSAGE    IF NEGATIVE (EXCLUSION) FILESETS ARE BEING USED,
                      THE FIRST (PRIMARY) FILESET MUST BE WILDCARDED OR
                      RECURSIVE.  (S/R 1007)

           CAUSE      You must include a wildcard character in your file
                      set to exclude afile set.

           ACTION     Retype the command using a wildcard character in
                      your file set.

-------------------------------------------------------------

1008         MESSAGE    SLASH "/" TO SPECIFY A LOCKWORD MAY ONLY BE
                      SUPPLIED AFTER THE FILE NAME PART OF A FILESET
                      NAME. SYNTAX
                      OF A LOCKWORDed FILE:
                      'FNAME/LOCKWORD[.GNAME[.ANAME]]' (S/R 1008)

           CAUSE      You did not type the lockword correctly.

           ACTION     Check the syntax and retype the command.

-------------------------------------------------------------

1009         MESSAGE    INVALID CHARACTER(S) IN LOCKWORD.  LOCKWORD MUST
                      BE ALPHANUMERIC BEGINNING WITH 'A-Z' AND BE NO MORE
                      THAN 8 CHARACTERS IN LENGTH. (S/R 1009)

           CAUSE      You did not enter a valid lockword.

           ACTION     Retype the command with a valid lockword.

-------------------------------------------------------------

1010         MESSAGE    UNMATCHED OPEN BRACKET '[' ENCOUNTERED IN
                      WILDCARED FILE NAME. BRACKETS ARE USED FOR
                      CHARACTER SET WILDCARDING.  THEY MAY NOT BE NESTED.
                      (S/R 1010)

           CAUSE      You entered the bracket incorrectly.

           ACTION     Check the syntax and retype the command.

-------------------------------------------------------------

1011         MESSAGE    UNMATCHED CLOSED BRACKET ']' ENCOUNTERED IN
                      WILDCARED FILE NAME. BRACKETS ARE USED FOR
                      CHARACTER SET WILDCARDING.  THEY MAY NOT BE NESTED.
                      (S/R 1011)

           CAUSE      You entered the bracket incorrectly.

           ACTION     Check the syntax and retype the command.

-------------------------------------------------------------

1012         MESSAGE    EXPECTED A '.', '/', ',', OR ';' TO FOLLOW THE
                      FILE NAME PART OF A FILESET.  '.' SPECIFIES A GROUP
                      NAME PART IS TO FOLLOW, '/' SPECIFIES A LOCKWORD IS
                      TO FOLLOW, ',' SEPARATES THIS FILESET FROM THE
                      NEXT, AND ';' SPECIFIES THE END OF THE FILESETLIST.
                      SYNTAX
                      'fname[/lockword][.gname[.aname]]'  (S/R 1012)

           CAUSE      You entered the file name syntax incorrectly.

           ACTION     Check the syntax and retype the command.

-------------------------------------------------------------

1013         MESSAGE    EXPECTED A '.', ',', OR ';' TO FOLLOW THE GROUP
                      NAME PART OF A FILESET.  '.' SPECIFIES A GROUP NAME
                      PART IS TO FOLLOW, ',' SEPARATES THIS FILESET FROM
                      THE NEXT, AND ';' SPECIFIES THE END OF THE
                      FILESETLIST. SYNTAX
                      'fname[/lockword][.gname[.aname]]'  (S/R 1013)

           CAUSE      You did not include a '.', ',', or ';' after the
                      group name.

           ACTION     Check the syntax and retype the command.

-------------------------------------------------------------

1014         MESSAGE    EXPECTED A ',', OR ';' TO FOLLOW THE ACCOUNT NAME
                      PART OF A FILESET. ',' SEPARATES THIS FILESET FROM
                      THE NEXT, AND ';'  SPECIFIES THE END OF THE
                      FILESETLIST. SYNTAX
                      'fname[/lockword][.gname[.aname]]'  (S/R 1014)

           CAUSE      You did not include a ',', or ';' after account
                      name.

           ACTION     Check the syntax and retype the command.

-------------------------------------------------------------

1015         MESSAGE    EXPECTED A FILE NAME PART NOT  A "-".  A "-" IS
                      USED TO SPECIFY NEGATIVE (EXCLUSION) FILESETS.
                      SYNTAX
                      'fname[/lockword][.gname[.aname]]'  (S/R 1015)

           CAUSE      You did not type the file name.

           ACTION     Enter a valid file name.

-------------------------------------------------------------

1016         MESSAGE    EXPECTED A GROUP NAME PART TO FOLLOW
                      'fname[/lockword].' INSTEAD OF A "-". A "-" IS USED
                      TO SPECIFY NEGATIVE (EXCLUSION) FILESETS. SYNTAX
                      'fname[/lockword][.gname[.aname]]'  (S/R 1016)

           CAUSE      You did not type the group name.

           ACTION     Enter a valid group name.

-------------------------------------------------------------

1017         MESSAGE    EXPECTED AN ACCOUNT NAME PART TO FOLLOW
                      'fname[/lockword].gname.', NOT  A "-".  A "-" IS
                      USED TO SPECIFY NEGATIVE (EXCLUSION) FILESETS.
                      SYNTAX
                      'fname[/lockword][.gname[.aname]]'  (S/R 1017)

           CAUSE      You did not type the account name.

           ACTION     Enter a valid account name.

-------------------------------------------------------------

1018         MESSAGE    EXPECTED A FILE NAME PART NOT  A "/".  A "/" IS
                      USED TO SPECIFY A LOCKWORD AFTER THE FILE NAME
                      PART. SYNTAX
                      'fname[/lockword][.gname[.aname]]'  (S/R 1018)

           CAUSE      You did not type the file name.

           ACTION     Enter a valid file name.

-------------------------------------------------------------

1019         MESSAGE    EXPECTED A GROUP NAME PART TO FOLLOW
                      'fname[/lockword].' NOT A "/". A "/" IS USED TO
                      SPECIFY A LOCKWORD AFTER THE FILE NAME PART. SYNTAX
                      'fname[/lockword][.gname[.aname]]'  (S/R 1019)

           CAUSE      You did not type the group name.

           ACTION     Enter a valid group name.

-------------------------------------------------------------

1020         MESSAGE    EXPECTED AN ACCOUNT NAME PART TO FOLLOW
                      'fname[/lockword].gname', NOT A "/".  A "/" IS USED
                      TO  SPECIFY A LOCKWORD AFTER THE FILE NAME PART.
                      SYNTAX
                      'fname[/lockword][.gname[.aname]]'  (S/R 1020)

           CAUSE      You did not type the account name.

           ACTION     Enter a valid account name.

-------------------------------------------------------------

1021         MESSAGE    EXPECTED A '.', ',', OR ';' TO FOLLOW THE
                      LOCKWORD PART OF A FILESET.  '.' SPECIFIES A GROUP
                      NAME PART IS TO FOLLOW, ',' SEPARATES THIS FILESET
                      FROM THE NEXT, AND ';' SPECIFIES THE END OF THE
                      FILESETLIST. SYNTAX
                      'fname[/lockword][.gname[.aname]]'  (S/R 1021)

           CAUSE      You did not include a '.', ',', or ';' after
                      lockword.

           ACTION     Check the syntax and retype the command.

-------------------------------------------------------------

1022         MESSAGE    LOCKWORDS ARE NOT ALLOWED IN NEGATIVE (EXCLUSION)
                      FILESETS. SYNTAX
                      'fname[.gname[.aname]]'  (S/R 1022)

           CAUSE      Same as message content.

           ACTION     Do not use lockwords with negative filesets.

-------------------------------------------------------------

1023         MESSAGE    SPECIFIED LOCKWORD IS TOO LONG.  THE MAXIMUM
                      LENGTH OF A LOCKWORD IS 8 CHARACTERS. SYNTAX
                      'fname[/lockword][.gname[.aname]]'  (S/R 1023)

           CAUSE      The maximum lockword length has been exceeded.

           ACTION     Enter a lockword with 8 characters or less.

-------------------------------------------------------------

1024         MESSAGE    INDIRECT FILES MAY NOT BE USED IN NEGATIVE
                      (EXCLUSION) FILESETS. SYNTAX
                      'fname[/lockword][.gname[.aname]][-
                      fname[.gname[.aname]]...'(S/R
                      1024)

           CAUSE      Same as message content.

           ACTION     Check the syntax and retype the command.

-------------------------------------------------------------

1025         MESSAGE    EXPECTED A FILENAME OF AN INDIRECT FILE TO FOLLOW
                      A '^' OR '!', NOT ANOTHER '^' OR '!'.  NOTE:  THE
                      CI USES '!' FOR VARIABLE SUBSITUTION SO USE OF '!'
                      SHOULD BE AVOIDED IN FAVOR OF '^'.  SYNTAX
                      '[^]fname[.gname[.aname]]'  (S/R 1025)

           CAUSE      You did not type the indirect file name correctly.

           ACTION     Check the syntax and retype the command.

-------------------------------------------------------------

1026         MESSAGE    EXPECTED A GROUP NAME PART TO FOLLOW
                      'fname[/lockword].', NOT A '^' OR '!'.  A '^' OR
                      '!' IS USED TO  SPECIFY AN INDIRECT FILE. SYNTAX
                      'fname[/lockword][.gname[.aname]]'  (S/R 1026)

           CAUSE      '^' or '!'  is not accepted after filename.

           ACTION     Check the syntax and retype the command.

-------------------------------------------------------------

1027         MESSAGE    EXPECTED AN ACCOUNT NAME PART TO FOLLOW
                      'fname[/lockword].gname.', NOT A '^' OR '!'.  A '^'
                      OR '!' IS USED TO  SPECIFY AN INDIRECT FILE. SYNTAX
                      'fname[/lockword][.gname[.aname]]'  (S/R 1027)

           CAUSE      '^' Or '!'  is not accepted after
                      filename.groupname.

           ACTION     Check the syntax and retype the command.

-------------------------------------------------------------

1028         MESSAGE    EXPECTED A FILESET NAME.  EMPTY FILESET NAMES ARE
                      NOT ALLOWED UNLESS THEY ARE USED SINGLY TO REQUEST
                      THE DEFAULT FILESET. Ex. 'STORE ;*t;SHOW'. SYNTAX
                      'fname[.gname[.aname]]'  (S/R 1028)

           CAUSE      You did not type the fileset name correctly.

           ACTION     Check the syntax and retype the command.

-------------------------------------------------------------

1029         MESSAGE    EXPECTED A GROUP NAME PART TO FOLLOW
                      'fname[/lockword].' INSTEAD OF A ",", ";" OR END OF
                      DATA. SYNTAX
                      'fname[/lockword][.gname[.aname]]'  (S/R 1029)

           CAUSE      You did not type a valid group name after file
                      name.

           ACTION     Check the syntax and retype the command.

-------------------------------------------------------------



MPE/iX 5.5 Documentation