PI74864: 'INVALID LINE COMMAND' ERROR WHEN ATTEMPTING TO EXECUTE DROP OR DDL LINE COMMAND FOR ALIAS OF A SEQUENCE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Attempting to use a line command such as DROP or DDL on an
  ALIAS of a SEQUENCE results in the message 'Invalid line
  command'.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Administration Tool             *
  *                 for z/OS and Object Comparison               *
  *                 Tool for z/OS.                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: Executing a line command                *
  *                      such as DROP or DDL on an               *
  *                      ALIAS of a SEQUENCE results in          *
  *                      the error message 'Invalid line         *
  *                      command'.                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Admin Tool and Object Comparison Tool did not support
  an ALIAS of a SEQUENCE. As a result, an attempt to
  execute a line command such as DROP or DDL on an
  ALIAS of a SEQUENCE would fail with the error message
  'Invalid line command'. AL and ALT functions on a sequence
  alias were also not supported.
  

Problem conclusion

• Problem has been resolved.
  
  New messages:
  Message# / Text
  ADBP016E The schema name of the target sequence cannot begin
   with 'SYS' unless the schema name is 'SYSADM'.
  Explanation
   A target sequence schema name that starts with 'SYS' but is
   not 'SYSADM' was entered. This is not allowed by DB2.
  System Action
   Processing stops.
  User Response
   Correct the schema name to proceed.
  
  Message# / Text
  ADBP017E The target sequence cannot be <parm>.
   Parameters
   <parm> Invalid sequence type. Possible values are:
  - a sequence generated for an identity column.
  - a sequence generated for a DOCID column.
  - an existing sequence alias.
  Explanation
   The target sequence name cannot identify any of the following:
   - a sequence that is generated by DB2 for an identity column
   - a sequence that is generated by DB2 for a DOCID column
   - an existing sequence alias
  System Action
   Processing stops.
  User Response
   Choose a valid target sequence to proceed.
  
  Message# / Text
   ADBP018W <parm> The sequence need not exist when the alias
   is defined, but it must exist when an SQL statement that
   contains the alias is used, otherwise an error is returned
   by DB2.
   Parameters
  <parm> is one of the following:
   - The target sequence does not exist.
   - A pending change to drop the target sequence exists.
  Explanation
   A target sequence name was entered for either a non-existent
   sequence, or one that will be dropped during the change
   management apply process. DB2 allows an alias to be created
   for such a sequence, but this may produce an error when an
   SQL statement that contains the alias is used.
  System Action
   The warning message is displayed on the panel.
  User Response
   Press ENTER to continue with ALT processing.
  
  Message# / Text
  ADBP019E Target sequence <sequence_name> for alias
   >alisas_name< must exist in order to proceed.
  Explanation
   Although it is possible to create a sequence alias that refers
   to a target sequence that does not currently exist, it is not
   possible to use that alias in an SQL statement such as ALTER.
  System Action
    Processing stops.
  User Response
    Create the target sequence that the alias refers to in order
   to proceed.
  
  Message# / Text
  ADBP01AW Target sequence name <sequence_name> will be
   substituted for the alias name in the ALTER statement. Press
   ENTER to continue.
  Explanation
   This warning message indicates that the target sequence name
   will be used instead of the sequence alias name in the ALTER
   statement that is built and executed. The effect is the same
   as using the alias name; both act upon the base object.
  System Action
   The warning message is displayed on the panel.
  User Response
   Press ENTER to continue with processing.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UI52912

Modules/Macros

•    ADBALT   ADBA1QA  ADBA1QI  ADBCCM   ADBCCME
  ADBCCMM  ADBCDTS  ADBCRCR  ADBCVCT  ADBCVOC  ADBCVSE  ADBE7QA0
  ADBHDIP  ADBHDIPD ADBH1A   ADBH6CL  ADBH6DT  ADBH7AD  ADBH7CA
  ADBH7QAL ADBPCP   ADBP01   ADBP7AD  ADBP7QAL ADBP7QA0 ADBP7SA0
  ADB1000  ADB2CME  ADB2CMF  ADB2CMO  ADB2CMP  ADB2CMR  ADB2CMS
  ADB2CMT  ADB2CMU  ADB2CM1  ADB2CM2  ADB2CM3  ADB2CVC  ADB2DEP
  ADB2DIP  ADB2DIPD ADB2GEN  ADB2GENS ADB2GENX ADB2GEN2 ADB2GEN6
  ADB2IGN  ADB2MSK  ADB2PA   ADB2PA3  ADB2PA6  ADB2RE   ADB2REE
  ADB2REH  ADB2REM  ADB2REP  ADB2RER  ADB2REU  ADB2REY  ADB2REZ
  ADB2WIN  ADB2WVL  ADB21    ADB21A   ADB21Q   ADB21QI1 ADB21T
  ADB21VV  ADB21Y   ADB26    ADB26CL  ADB26CTQ ADB26DT  ADB26RT
  ADB27CA  ADB27CAA ADB27CMR ADB27CR  ADB27C0
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RB20 PSY UI52912

     UP17/12/27 P F712

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.