IBM Support

IT04057: ANS1149E MESSAGE AND DOMAIN OPTION NEED CLARIFICATION.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The user reponses for message ANS1149E are not complete and the
    information for the DOMAIN statement is not as clear as it could
    be.
    For the error message ANS1149E, this is the current message:
    ANS1149E  No domain is available for incremental backup. The
    domain may be empty or all file systems in the domain are
    excluded.
    Explanation: An incremental backup was started, but no domain
    was selected. There are two possible reasons for this message:
    
    *  The client is a diskless workstation for which no local file
    systems exist.
    
    *  An attempt was made to back up a file system that is excluded
    with the EXCLUDE.FS option.
    
    System action: processing stops.
    User response: Choose a domain and restart the incremental
    backup. Make sure that the DOMAIN statement specifies the file
    systems you wish to back up.
    Prevent this message by not trying to back up the file system
    that is excluded with EXCLUDE.FS. If this file system should be
    backed up, then remove the EXCLUDE.FS option.
    The explanation limits the cause to only two possible reasons,
    there are other possible causes that will result in this message
    being displayed.
    Another possible cause should be added to the explanation:
    A DOMAIN option that only subtracts file systems was specified
    and no other explicit DOMAIN option exists to specify which file
    systems should be processed. For example, if no DOMAIN option is
    specified in the client options file but a client option set
    includes a DOMAIN option that subtracts a file system.
    As "diskless workstations" do not appear to be very common,
    perhaps this should be demoted to the last possible reason.
    To the user response, we can suggest checking the client option
    file, client option set, schedule defined on the TSM server, and
    command line arguments, for DOMAIN options that only subtract
    file systems, but do not explicitly specify file systems that
    should be processed.
    For the reference information for DOMAIN, the documentation
    should be updated to make it clearer that if you have a DOMAIN
    statement that only subtracts file systems, you need to also
    have a DOMAIN statement that includes file systems to process.
    The following text (2nd paragraph) could be added after the
    existing paragraph:
    You can exclude objects from the domain by specifying the
    exclusion operator (-) before the object. If any domain
    definition excludes an object, that object is excluded from the
    domain, even if another definition includes the object. You
    cannot use the domain exclusion operator (-) in front of any
    domain keyword that begins with all-.
    If a domain statement excludes one or more objects but no domain
    statement includes any objects, then the result is an empty
    domain. Therefore you must explicitly specify objects to be
    included in the domain if any domain statements exclude objects.
    An explicit example that illustrates this:
    The following domain statement yields and empty domain, which
    means that nothing will be backed up:
    domain -systemstate
    The following domain statement yields a domain that consists of
    all local file systems but not system state:
    domain all-local -systemstate
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Backup-archive client version 6.4.2          *
    *                 running on all platforms                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: See ERROR DESCRIPTION                   *
    ****************************************************************
    * RECOMMENDATION: Apply fixing level when available. This      *
    *                 problem is currently projected to be fixed   *
    *                 in levels 6.4.3 and 7.1.2. and in the        *
    *                 documentation  Note that this is subject     *
    *                 to change at the discretion of IBM.          *
    ****************************************************************
    *
    

Problem conclusion

  • The problem described in this APAR has been fixed so that it
    no longer occurs.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT04057

  • Reported component name

    TSM CLIENT

  • Reported component ID

    5698ISMCL

  • Reported release

    64W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-08-27

  • Closed date

    2014-10-15

  • Last modified date

    2014-10-15

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

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

Fix information

  • Fixed component name

    TSM CLIENT

  • Fixed component ID

    5698ISMCL

Applicable component levels

  • R64A PSY

       UP

  • R64H PSY

       UP

  • R64L PSY

       UP

  • R64M PSY

       UP

  • R64S PSY

       UP

  • R64W PSY

       UP

  • R71A PSY

       UP

  • R71H PSY

       UP

  • R71L PSY

       UP

  • R71M PSY

       UP

  • R71S PSY

       UP

  • R71W PSY

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"64W","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
08 January 2022