TAASYSTEM -- TAA Tools System Considerations

TAA Productivity Tools System Considerations
The installation of the TAA Productivity Tools is designed so that system changes are minimal. - TAAxxx libraries will be temporarily added as part of the installation process. These libraries will be deleted as part of a successful installation. See the later discussion. - Three libraries (TAATOOL, TAASECURE, TAAWORK) will be added permanently to your system if they do not already exist. - TAAxxx Authorization lists will be added to your system if they do not already exist. No changes occur to existing authorization lists allowing you to authorize users to TAA function only once. The installation of the TAA Productivity Tools is designed as follows: - No system values are changed. - No network attributes are changed. - No work management objects are changed (such as subsystem descriptions or job queues). -- Special TAA subsystems and job queues will exist in TAATOOL such as that provided by the SAVACT tool (TAASBS and TAAJOBQ) and the UPSMON tool (TAAUPSMON and TAAUPSMON). These objects are not used unless you are using the specific tools. - The UPSMON job description is shipped with USRPRF(QPGMR) and is owned by QSECOFR. The QPGMR profile is not authorized until an ALLOBJ user runs the STRUPSMON2 command to add auto start job to the controlling subsystem. - The JOBACT job description is shipped with USRPRF(QPGMR) and is owned by QSECOFR. The QPGMR profile is not authorized until an ALLOBJ user runs the STRJOBACT2 command to add auto start job to the controlling subsystem. - No changes occur to the system objects used for job time dependent scheduling. - No system commands are changed (such as command defaults). - The user profile TAAJOBCTL is added to your system if it does not already exist. This profile is set to PASSWORD(NONE) and SPCAUT(JOBCTL). One or more programs are changed so that TAAJOBCTL becomes the owner and can only adopt JOBCTL special authority. No other profiles are added or changed. - No system supplied files are changed. - No objects in the QSYS library with the exception of the libraries (TAATOOL, TAASECURE, and TAAWORK) and the TAAxxx authorization lists are created. - No changes to the QGPL library or any objects within the library occurs. Some tools place objects in QGPL. These objects will not exist unless the tools are used such as SYSHST (creates the SYSHSTP file) and SAVACT (creates the TAASAVACTP file). Libraries During the installation phase, the libraries TAAINS, TAAINS2, TAAINSLIC, TAAINS2Z, TAATOOLZ, TAATOOLZ2, and TAASECUREZ are created or restored. A successful installation causes these libraries to be deleted automatically. The installation of the TAA Productivity Tools causes three libraries to be permanently added if they do not already exist: TAATOOL Contains the majority of code and commands. TAASECURE Contains secure objects. TAAWORK Contains work objects for various tools. Some users may prefer a separate library for the TAA Tool commands. See the discussion in the 'Library List' information member on the HELPTAA menu. A copy of all TAA commands will exist in TAATOOL. A duplicate of the commands may also exist in another library. A unique library may be created for this purpose or an existing library may be used. If a unique library is to be created, TAACMD is the recommended name. The command library will also contain: - Any TAA menus such as HELPTAA. - A few physical files that are used for external file descriptions by some tools. An installation option will allow you to name a command library or you may create one after installation with the DUPTAACMD tool. Some tools require the use of other libraries which you may need to create. Authorization lists Several TAAxxx authorization lists will be created if they do not already exist. They are used to provide a means to authorize certain security sensitive tools. Using an authorization list allows the next release of the TAA Productivity Tools to be installed without changing your authorizations. For a discussion of the specific authorization lists, see the 'TAA Tool Security' option on the HELPTAA menu. The CHKTAAAUT tool exists to allow you to compare your current authorizations to TAA objects versus the way they were shipped. Ownership Almost all of the TAA Productivity Tool objects are owned by QSECOFR. You should not change the ownership of the objects. During the install, the special profile TAAJOBCTL is created if it does not already exist. It is set to PASSWORD(NONE) and SPCAUT(JOBCTL). One or more programs are changed so that TAAJOBCTL becomes the owner. This allows certain programs to only adopt the JOBCTL special authority and not the full authority of QSECOFR. Security statement The TAA Productivity Tools are designed so that their use does not violate any system security functions. Objects and data are read using standard system interfaces such as system commands, system APIs, CL and RPG. Some of the programs use the program adopt function where the USRPRF program attribute is set to OWNER. These programs have been designed to be safely used by authorized individuals. Calls to sub functions are library qualified to the TAATOOL library and OVR commands specify SECURE(YES). You have a responsibility to provide a secure system environment that allows the TAA program design to protect your installation. See the discussion in the 'TAA Tool Security' information member on the HELPTAA display. Subsystem descriptions The TAASBS subsystem exists in TAATOOL. It is used internally by the SAVACT tool. The TAAUPSMON subsystem exists in TAATOOL. It is used internally by the UPSMON tool. Job queue The TAAJOBQ job queue exists in TAATOOL. It is used internally by the SAVACT tool. The TAAUPSMON job queue exists in TAATOOL. It is used internally by the UPSMON tool. Output queue An output queue named TAAOUTQ is shipped in TAATOOL. This is used by CRTTAATOOL and a few other tools. A second output queue name TAAOUTQ2 is also shipped. It is used by CHKSPLCTL. Message file A message file named TAAMSGF is shipped in TAATOOL. It will contain a few message descriptions that are used by the tools and also blank message IDs (similar to CPF9898) which are used by the tools and may be used in user applications. A message file TAAMNUAM will also be in TAATOOL and is part of the DYNMNU tool. Source files Several source files are shipped in the TAATOOL library for use by various tools and for your own use. Printer files Several printer files are shipped in the TAATOOL library for use by various tools and for your own use. Most programs output to QPRINT or TAAPRT1 and use OVRPRTF to change the name of the spooled file to a name meaningful to the function or the objects specified (such as the library name specified on a command). Unique printer files such as TAAPRT2 and TAAPRT3 are used to provide separate files when a tool that causes printed output also invokes a tool that also causes printed output. TIMRCD Journal The TIMRCD journal is required for use by the TIMRCD tool. The journal is not shipped with the TAA Productivity Tools. A different journal may be used, but the suggested solution is to create the TIMRCD journal using the CRTTIMRCDJ command. Backup See the HELPTAA option for Backup and the separate option for Disaster Recovery. Copyright TAA Tools, Inc. 1995, 2021

TAA Productivity Tools System Considerations

The installation of the TAA Productivity Tools is designed so that
system changes are minimal.

-   TAAxxx libraries will be temporarily added as part of the
    installation process. These libraries will be deleted as part of a
    successful installation. See the later discussion.

-   Three libraries (TAATOOL, TAASECURE, TAAWORK) will be added
    permanently to your system if they do not already exist.

-   TAAxxx Authorization lists will be added to your system if they do
    not already exist. No changes occur to existing authorization
    lists allowing you to authorize users to TAA function only once.

The installation of the TAA Productivity Tools is designed as follows:

-   No system values are changed.

-   No network attributes are changed.

-   No work management objects are changed (such as subsystem
    descriptions or job queues).

    -- Special TAA subsystems and job queues will exist in TAATOOL
    such as that provided by the SAVACT tool (TAASBS and TAAJOBQ) and
    the UPSMON tool (TAAUPSMON and TAAUPSMON). These objects are not
    used unless you are using the specific tools.

-   The UPSMON job description is shipped with USRPRF(QPGMR) and is
    owned by QSECOFR. The QPGMR profile is not authorized until an
    *ALLOBJ user runs the STRUPSMON2 command to add auto start job to
    the controlling subsystem.

-   The JOBACT job description is shipped with USRPRF(QPGMR) and is
    owned by QSECOFR. The QPGMR profile is not authorized until an
    *ALLOBJ user runs the STRJOBACT2 command to add auto start job to
    the controlling subsystem.

-   No changes occur to the system objects used for job time dependent
    scheduling.

-   No system commands are changed (such as command defaults).

-   The user profile TAAJOBCTL is added to your system if it does not
    already exist. This profile is set to PASSWORD(*NONE) and
    SPCAUT(*JOBCTL). One or more programs are changed so that
    TAAJOBCTL becomes the owner and can only adopt *JOBCTL special
    authority.

    No other profiles are added or changed.

-   No system supplied files are changed.

-   No objects in the QSYS library with the exception of the libraries
    (TAATOOL, TAASECURE, and TAAWORK) and the TAAxxx authorization
    lists are created.

-   No changes to the QGPL library or any objects within the library
    occurs. Some tools place objects in QGPL. These objects will not
    exist unless the tools are used such as SYSHST (creates the
    SYSHSTP file) and SAVACT (creates the TAASAVACTP file).

Libraries

During the installation phase, the libraries TAAINS, TAAINS2,
TAAINSLIC, TAAINS2Z, TAATOOLZ, TAATOOLZ2, and TAASECUREZ are created
or restored. A successful installation causes these libraries to be
deleted automatically.

The installation of the TAA Productivity Tools causes three libraries
to be permanently added if they do not already exist:

        TAATOOL      Contains the majority of code and commands.
        TAASECURE    Contains secure objects.
        TAAWORK      Contains work objects for various tools.

Some users may prefer a separate library for the TAA Tool commands.
See the discussion in the 'Library List' information member on the
HELPTAA menu. A copy of all TAA commands will exist in TAATOOL. A
duplicate of the commands may also exist in another library. A unique
library may be created for this purpose or an existing library may be
used. If a unique library is to be created, TAACMD is the recommended
name.

The command library will also contain:

-   Any TAA menus such as HELPTAA.

-   A few physical files that are used for external file descriptions
    by some tools.

An installation option will allow you to name a command library or you
may create one after installation with the DUPTAACMD tool.

Some tools require the use of other libraries which you may need to
create.

Authorization lists

Several TAAxxx authorization lists will be created if they do not
already exist. They are used to provide a means to authorize certain
security sensitive tools.

Using an authorization list allows the next release of the TAA
Productivity Tools to be installed without changing your
authorizations.

For a discussion of the specific authorization lists, see the 'TAA
Tool Security' option on the HELPTAA menu.

The CHKTAAAUT tool exists to allow you to compare your current
authorizations to TAA objects versus the way they were shipped.

Ownership

Almost all of the TAA Productivity Tool objects are owned by QSECOFR.
You should not change the ownership of the objects.

During the install, the special profile TAAJOBCTL is created if it
does not already exist. It is set to PASSWORD(*NONE) and
SPCAUT(*JOBCTL). One or more programs are changed so that TAAJOBCTL
becomes the owner. This allows certain programs to only adopt the
*JOBCTL special authority and not the full authority of QSECOFR.

Security statement

The TAA Productivity Tools are designed so that their use does not
violate any system security functions. Objects and data are read using
standard system interfaces such as system commands, system APIs, CL
and RPG.

Some of the programs use the program adopt function where the USRPRF
program attribute is set to *OWNER. These programs have been designed
to be safely used by authorized individuals. Calls to sub functions
are library qualified to the TAATOOL library and OVR commands specify
SECURE(*YES).

You have a responsibility to provide a secure system environment that
allows the TAA program design to protect your installation. See the
discussion in the 'TAA Tool Security' information member on the
HELPTAA display.

Subsystem descriptions

The TAASBS subsystem exists in TAATOOL. It is used internally by the
SAVACT tool.

The TAAUPSMON subsystem exists in TAATOOL. It is used internally by
the UPSMON tool.

Job queue

The TAAJOBQ job queue exists in TAATOOL. It is used internally by the
SAVACT tool.

The TAAUPSMON job queue exists in TAATOOL. It is used internally by
the UPSMON tool.

Output queue

An output queue named TAAOUTQ is shipped in TAATOOL. This is used by
CRTTAATOOL and a few other tools. A second output queue name TAAOUTQ2
is also shipped. It is used by CHKSPLCTL.

Message file

A message file named TAAMSGF is shipped in TAATOOL. It will contain a
few message descriptions that are used by the tools and also blank
message IDs (similar to CPF9898) which are used by the tools and may
be used in user applications.

A message file TAAMNUAM will also be in TAATOOL and is part of the
DYNMNU tool.

Source files

Several source files are shipped in the TAATOOL library for use by
various tools and for your own use.

Printer files

Several printer files are shipped in the TAATOOL library for use by
various tools and for your own use. Most programs output to QPRINT or
TAAPRT1 and use OVRPRTF to change the name of the spooled file to a
name meaningful to the function or the objects specified (such as the
library name specified on a command).

Unique printer files such as TAAPRT2 and TAAPRT3 are used to provide
separate files when a tool that causes printed output also invokes a
tool that also causes printed output.

TIMRCD Journal

The TIMRCD journal is required for use by the TIMRCD tool. The journal
is not shipped with the TAA Productivity Tools. A different journal
may be used, but the suggested solution is to create the TIMRCD
journal using the CRTTIMRCDJ command.

Backup

See the HELPTAA option for Backup and the separate option for Disaster
Recovery.

Copyright TAA Tools, Inc. 1995, 2021

Added to TAA Productivity tools April 1, 1995

Home Page

Up to Top