VM65269: UNABLE TO SEND XAUTOLOG CONSOLE INPUT WITH AT CMD

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The XAUTOLOG command allows the command issuer to specify
  console input that is treated as virtual console input for
  the user that is being XAUTOLOGged, in response to the first
  read issued by the user's virtual machine.
  
  However, if an XAUTOLOG with console input is executed in
  an SSI cluster with the AT command to another member of the
  cluster, the text following the LINEND character is executed
  locally by the AT command issuer, and not by the user being
  XAUTOLOGged on the target member.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users who issue the XAUTOLOG command         *
  *                 with the AT command.                         *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION: APPLY PTF                                    *
  ****************************************************************
  The XAUTOLOG command allows the command issuer to specify
  console input that is treated as virtual console input for
  the user that is being XAUTOLOGged, in response to the first
  read issued by the user's virtual machine.
  
  However, if an XAUTOLOG with console input is executed in
  an SSI cluster with the AT command to another member of the
  cluster, the text following the LINEND character is executed
  locally by the AT command issuer, and not by the user being
  XAUTOLOGged on the target member.
  
  For example, let us say we have a 2 member SSI cluster with
  members named SYSTEM1 and SYSTEM2.  USERA on SYSTEM1, who is
  using the default LINEND character of '#', issues this command:
  
  AT SYSTEM2 CMD XAUTOLOG USERB #CP MSG OPERATOR HELLO
  
  In this case, the user's intent is to have USERB on SYSTEM2
  issue the MSG command to the OPERATOR on SYSTEM2 after he is
  logged on.  However, what happens instead is that USERB is
  logged onto SYSTEM2, but USERA on SYSTEM1 issues the MSG
  command to OPERATOR on SYSTEM1.
  

Problem conclusion

• HCPAUP is updated to support a new CMD option, which
  allows users to specify a single command string that will
  be executed by the user that is being logged on with the
  XAUTOLOG command.  In the scenario described earlier in
  this APAR, the following command would be used to logon
  USERB on SYSTEM2, and have USERB send a message to the
  OPERATOR on SYSTEM2:
  
  AT SYSTEM2 CMD XAUTOLOG USERB CMD CP MSG OPERATOR HELLO
  
  The following updates are being made to the CP Commands
  and Utilities Reference manual, SC24-6175:
  
  The command diagram is updated for the CMD option:
  
   >--.--------------------------.-------------------------><
      |-CMD console_input_data-' |
      '-#console_input_data-'    '
  
  The following description is added for the CMD option:
  
    CMD console_input_data
        specifies the data that you want used as virtual
        console input in response to the first read issued
        by the user's virtual machine.  You may use the
        remainder of the command line to enter console data.
  
        Note:  This option differs from #console_input_data
        below in that logical line-end characters are not
        honored.  Because of this, only one command can be sent.
        This option is intended to be used when the XAUTOLOG
        command is issued with the AT command to a remote
        member of the SSI cluster.  It can also be used if the
        user being logged on is on the same system, with
        or without the AT command.
  

Temporary fix

• FOR RELEASE VM/ESA CP/ESA R620 :
  PREREQ: VM65333
  CO-REQ: NONE
  IF-REQ: NONE
  FOR RELEASE VM/ESA CP/ESA R630 :
  PREREQ: VM65333
  CO-REQ: NONE
  IF-REQ: NONE
  

Comments

APAR Information

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

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

  UM34102 UM34103

Modules/Macros

• HCPAUP   XAUTOLOG
  

Fix information

• Fixed component name

  VM CP

• Fixed component ID

  568411202

Applicable component levels

• R620 PSY UM34102

     UP13/09/03 P 1401

• R630 PSY UM34103

     UP13/09/03 P 1401

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.