IC72052: TIVOLI STORAGE MANAGER V6.2 CLIENT PROMPTED SCHEDULE MISSED WHEN RUNNING MULTIPLE SCHEDULERS WITH THE SAME TCPCLIENTPORT VALUE.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • A TSM client scheduler is started in prompted mode.
    The TSM client schedule log shows the client is waiting to be
    contacted by the server. For example :
    
    10/13/2010 14:05:46 ANS0991I TSM scheduler is listening for
     server requests on port 1501
    10/13/2010 14:05:46 TSM Backup-Archive Client Version
     6, Release 2, Level 1.0
    10/13/2010 14:05:46 Querying server for next scheduled event.
    10/13/2010 14:05:46 Node Name: NODE1
    10/13/2010 14:05:46 Session established with server TSM1: AIX
    10/13/2010 14:05:46   Server Version 6, Release 1, Level 3.2
    10/13/2010 14:05:46   Server date/time: 10/13/2010 15:05:43
      Last access: 10/13/2010 15:05:41
    10/13/2010 14:05:46 --- SCHEDULEREC QUERY BEGIN
    10/13/2010 14:05:46 --- SCHEDULEREC QUERY END
    10/13/2010 14:05:46 Next operation scheduled:
    10/13/2010 14:05:46 --------------------------------------------
    10/13/2010 14:05:46 Schedule Name:         INCREMENTAL_BKUP
    10/13/2010 14:05:46 Action:                Incremental
    10/13/2010 14:05:46 Objects:
    10/13/2010 14:05:46 Options:
    10/13/2010 14:05:46 Server Window Start:  00:00:00 on 10/14/2010
    10/13/2010 14:05:46 --------------------------------------------
    10/13/2010 14:05:46 Waiting to be contacted by the server.
    
    A schedule is defined to start at 16:00 but the schedule does
    not run. The TSM server activity log shows :
    
    10/13/2010 15:30:00      ANR2017I Administrator ADMIN issued
     command: DEFINE SCHEDULE MYDOM TEST startt=16:00
     startd=today duru=min dura=5
    10/13/2010 15:30:30      ANR2017I Administrator ADMIN issued
     command: DEFINE ASSOCIATION MYDOM TEST NODE1
    ...
    10/13/2010 16:00:00      ANR2561I Schedule prompter contacting
     NODE1 (session nnn) to start a scheduled operation.
    10/13/2010 16:00:01      ANR0403I Session nnn ended for node
     NODE1 ().  (SESSION: 3628)
    
    The above ANR2561I/ANR0403I messages repeat themselves every
    thirty (30) seconds until the schedule is eventually missed
    and the following message is logged when the scheduler window
    has elapsed :
    
    10/13/2010 16:05:10      ANR2578W Schedule TEST in domain MYDOM
     for node NODE1 has missed its scheduled start up window.
    
    Customer/L2 Diagnostics:
    A TSM client service trace will show the client is waiting to
    be contacted by the server. For example :
    
    10/13/2010 14:05:46.793 [006424] [5976] : commtcp.cpp    (2930):
     TCP Driver Ready for connections on Port 1501
    10/13/2010 14:05:46.949 [006424] [5976] : session.cpp    (1038):
     sessInit: Session initialized.
    10/13/2010 14:05:46.949 [006424] [5976] :
     DccSessionRequestor.cpp( 335): getConnection(): Entering
    10/13/2010 14:05:46.949 [006424] [5976] :
     DccSessionRequestor.cpp( 365): getConnection(): calling
     acceptOne() with waitTime = 0
    10/13/2010 14:05:46.949 [006424] [5976] : pscomtcp.cpp   ( 701):
     psTcpSetNonBlocking: successfully set v4 socket to be
     non-blocking.
    10/13/2010 14:05:46.949 [006424] [5976] : commtcp.cpp    (3024):
     TcpAcceptInbound: using non-blocking sockets
    10/13/2010 14:05:46.964 [006424] [5976] : pscomtcp.cpp   ( 876):
     psIsSocketReady(): timed out!
    10/13/2010 14:05:47.980 [006424] [5976] : pscomtcp.cpp   ( 876):
     psIsSocketReady(): timed out!
    ...etc
    (no schedule is launched)
    
    The netstat command will show that more than one process is
    listening on port 1501. For example :
    
    C:\>netstat -ano
    
    Active Connections
    
    Proto  Local Address   Foreign Address     State           PID
    ...
    TCP    0.0.0.0:1501    0.0.0.0:0           LISTENING       3104
    TCP    0.0.0.0:1501    0.0.0.0:0           LISTENING       1700
    TCP    0.0.0.0:1501    0.0.0.0:0           LISTENING       3936
    ...etc
    
    In this case, the prompted schedule is missed because there are
    multiple TSM client scheduler processes running and listening on
    the same 1501 port.
    
    When, the TCPCLIENTPORT is NOT set, the default value of 1501
    is used, If that port is already in use, a new dynamic port
    should be aquired. Instead, the client listens on the same 1501
    port.
    
    When the TCPCLIENTPORT is set and the specified port is in use,
    the ANS1018E should be issued and the scheduler should end.
    Instead, the client runs and listens on the same tcpclientport
    value.
    
    The same issue also exists with the Client Acceptor service
    (dsmcad) and Remote Client Agent (dsmagent) services.
    In particular, the dsmcad functionality will be affected if
    multiple dsmcad services use the same WEBPORTS values.
    
    TSM Versions Affected:
    TSM client v6.2 client on Windows only.
    
    Additional Keywords:
    zz62 sched prompt dsmcad.exe dsmagent.exe dsmcsvc.exe
    

Local fix

  • Use one of the following options :
    1) Use a different TCPCLIENTPORT value for each scheduler
       running in prompted mode on the same machine.
    2) Use the POLLING schedule mode.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Backup-archive versions 6.2.0 and 6.2.1      *
    *                 running on Microsoft Windows                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: See ERROR DESCRIPTION                   *
    ****************************************************************
    * RECOMMENDATION: Apply fixing level when available. This      *
    *                 problem is currently projected to be fixed   *
    *                 in level 6.2.2. Note that this is subject    *
    *                 to change at the discretion of IBM.          *
    ****************************************************************
    On Microsoft Windows, multiple scheduler processes can listen
    to the same port, which prevents schedules from running
    successfully.
    

Problem conclusion

  • The backup-archive client has been fixed so that it behaves as
    follows:
    
     - If TCPCLIENTPORT is not set and the default port number
       (1501) is in use, the client will attempt to find another
       port number on which to listen for scheduled events.
    
     - If TCPCLIENTPORT is set and the specified port is in use,
       message ANS1018E will be issued to indicate that the port
       is in use. The client will not be able to listen for
       scheduled events, so schedled events will not run.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC72052

  • Reported component name

    TSM CLIENT

  • Reported component ID

    5698ISMCL

  • Reported release

    62W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-10-20

  • Closed date

    2010-10-29

  • Last modified date

    2010-10-29

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

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

Modules/Macros

  • DSMC     DSMCAD   DSMSVC
    

Fix information

  • Fixed component name

    TSM CLIENT

  • Fixed component ID

    5698ISMCL

Applicable component levels

  • R62W PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Storage Manager

Software version:

62W

Reference #:

IC72052

Modified date:

2010-10-29

Translate my page

Machine Translation

Content navigation