TAA Tools
                      Backup Considerations

The following is recommended:

  **   A full  library save such  as SAVLIB  LIB(*ALLUSR) on a  regular
       basis of the TAATOOL, TAASECURE, and TAAWORK libraries.

  **   A  full  library  save   such  as  SAVLIB  LIB(*ALLUSR)  of  any
       libraries  (or  files  created  in  other  libraries) associated
       with the TAA Tools.

  **   A regular SAVSYS or  SAVSECDTA to capture the TAA  Authorization
       Lists and their authorizations.

  **   If  you use  a SAVCHGOBJ  approach  on a  daily basis,  consider
       including  the TAATOOL  and TAASECURE  libraries to  capture any
       daily changes along  with your other libraries.   The amount  of
       change activity  from TAATOOL  and TAASECURE  should be  none or
       very little.

If  you are using  a SAVCHGOBJ approach  on a daily  basis, the TAAWORK
library may  be bypassed.    This library  only contains  work  objects
which do not need to be saved.

The  following  describes  the  major  pieces  that  make  up  the  TAA
Productivity Tools product and any unique backup considerations.


The  TAATOOL  library   contains  mostly  programs,  commands,  display
files,  and model  files (used  to create  physical files from).   Very
few of the objects will have any changes made to them.

For example:

  **   The QATTxxx  source files  in  TAATOOL are  intended to  contain
       source you  have copied out of  the TAA Archive that  you do not
       intend  to change permanently,  but want a  copy for  use in SEU
       copying or browsing.  If  a back level version is restored,  the
       source could  be copied  out again  (See the  discussion on  the
       HELPTAA menu for 'Modifying a Tool').

  **   The  QATTDDS source file in  TAATOOL will contain  source if you
       have a demonstration  license.   This source is  used to  create
       files such as with the SPLARC tool.

  **   The PRTDBFSRC  source  file in  TAATOOL is  intended to  contain
       the  source  created  by CRTPRTPGM  (it  is  the default  source
       file).   By  default, the  member is  removed after  the program

  **   Some data  areas in  TAATOOL  are used  for recovery  processing
       while a tool is running.

With normal  use, there  will probably  be few if  any changes  made to
the  TAATOOL  library  on  a  daily  basis.    However,  you  have  the
capability to modify tools and  re-create them in the TAATOOL  library.
Any of these types of changes should be backed up regularly.


The  TAASECURE  library is  used  for  security sensitive  objects  and
allows  the Security  Officer to  make entries  that control  how other
tools are processed.

For example:

  **   The data area  ADPMBR is used  by the ADPMBR  tool to  determine
       what  files  are  valid  for  the  use  of  a  command  such  as

  **   The  data  area  ACCSECLIB is  used  by  the  ACCSECLIB tool  to
       determine  what private libraries  may be used  by the ACCSECLIB

  **   The  DSPPWD  tool  is  designed  to  allow  a  capture  of  user
       passwords so  that the  actual passwords may  be reviewed.   The
       file  containing  the  passwords  is  kept  in  TAASECURE.    No
       entries will  be  made  unless  the Security  Officer  makes  an
       overt act to  implement the steps needed to  activate the DSPPWD

There  will  probably be  few  if  any changes  made  to  the TAASECURE
library on a  daily basis.   However,  there are  a few  tools such  as
DSPPWD  and  CHGUSRPWD2  where  use  of  the  tools  require  that  you
re-create the  tools with some objects being placed  in TAASECURE.  Any
of these types of changes should be backed up regularly.


The  TAAWORK library  is used  for various  work objects.   The library
must exist for certain  tools, but the objects  in the library are  not
needed  beyond an  IPL.   The tools  that use  the library  provide for
cleanup functions.

TAA Authorization Lists

Several  tools are  security controlled  by TAAxxx  Authorization lists
that exist  in QSYS.   The  use of  Authorization Lists  allows you  to
grant authority  to use various tools  and retain the authority  when a
new update or release of the TAA Productivity Tools is installed.

The system  saves Authorization Lists in QSYS  when SAVSYS or SAVSECDTA
is used.  A regular use of these commands is recommended.

There  will  probably  be   few  if  any  changes   made  to  the   TAA
Authorization Lists on a daily basis.

TAAINS and TAAINSLIC libraries

The TAAINS  and TAAINSLIC  libraries are  used for  installing the  TAA
Productivity Tools.   After the  successful installation of  the tools,
the  libraries are  automatically deleted.   The libraries  do not need
to exist permanently on  your system and do  not need to be  backed up.

Other Special Install Libraries

During  the install  process, the  TAAINS2 library  is created  on your
system.     It  will  be  automatically   deleted  if  the  product  is
successfully  restored.     The  library   does  not   need  to   exist
permanently on your system and does not need to be backed up.

The TAATOOLZ,  TAASECUREZ, and  TAAINS2Z are  restored as  part of  the
install  process and  deleted shortly  after they  are restored.   They
are used  to set  the user  attribute of  the corresponding  libraries.
They  should  not  exist  on  your  system  if  the  product  has  been
successfully restored.

TAACMD Library

The TAACMD  library is not a formal part  of the TAA Productivity Tools
product.   This is the recommended name  for the library to contain the
commands if you want a separate library for the TAA commands.

A separate library  is optional.  See  the discussion in 'Library  List
Requirements' on the HELPTAA menu.

If you have  such a library, it  should be backed up as  your own data.

There  will  probably  be  few if  any  changes  made  to  the separate
command library on a daily basis.

TAAFILE library

The name  TAAFILE  is  are  not  part of  the  TAA  Productivity  Tools
product.  When the  TAA tools of QUSRTOOL were  being used, the TAAFILE
library  was  often  used to  contain  the  files  required by  certain
tools.  When  the TAA  Productivity Tools product  was introduced,  the
commands that created files  allowed the user to decide  the library to
be used.

If  you are still  using TAAFILE,  you should  review the objects.   If
they are no longer being used, you may delete the library.

Some  users may  prefer to  keep all  TAA created  files in  a specific
library in which case any name may be used.

Other Tool Libraries

Certain tools  require you  to create  libraries of  specific names  or
optionally  require you  to  create such  a  library.   Each tool  that
requires   such   a   library   will   normally   discuss  the   backup

For example:

  **   The SPLCTL  tool  requires  that  you  create  the  SPLCTLS  and
       SPLCTLD libraries.   These libraries will contain  your data and
       will probably have a significant amount of daily changes.

  **   The  CHKSPELL   tool  (also  the  other  tools  involving  spell
       checking)  optionally   allow   the   entry   of   a   list   of
       dictionaries.   These  dictionary  lists (in  the  form of  data
       areas) must  exist in the  TAADCT library.  You  must create the
       library  and other objects  in the library if  you want to enter
       a list of  standard dictionaries instead  of using the  default.
       There will  probably be  few if any  changes made to  the TAADCT
       library on a daily basis.

Created Files and Other Objects

Some  of the tools  support CRT or  CVT commands that  will create data
base files and  other objects  in a  library that you  specify.   These
libraries  should be  backed up  regularly  as they  will contain  your

The amount  of change to the data  will vary significantly depending on
the tool.


Because the TAA Productivity  Tools can be helpful  in a total  restore
situation, some users may  prefer to restore the TAATOOL  and TAASECURE
libraries before restoring the normal set of libraries.

For   example,  the   system  commands   RSTLIB  LIB(*IBM)   or  RSTLIB
LIB(*NONSYS)  require the  restricted state.   If  you want  to restore
without  using  the   restricted  state,  RSTALLLIB  may   be  helpful.
RSTALLLIB  has been  used  to successfully  restore  without using  the
restricted  state,  but since  the  function  is not  supported  by the
system, you run at your own risk.  There are no known problems.

RSTALLLIB has the additional benefit  that it has both a beginning  and
ending file  sequence number  as parameters  on the  command.  Thus  if
you  have multiple  tape devices  and a  high speed  CPU, you  can have
multiple restore operations in process at the same time.

The SAVTAATOOL tool  requires that either  the $$TAATOOL or  Q$$TAATOOL
library be  created by  using the  CRTSAVTAA command which  is part  of
the same  tool.  You  then save to  either library with  the SAVTAATOOL
command.    The  intent  of  using  these  library  names  is  that the
libraries would be saved at  the beginning (or close to  the beginning)
of  a tape created  by one  of the  special values  for the  SAVLIB LIB

For example,  if you want to use the TAA  Tools to help you restore the
system, you would  choose one of  the special libraries  based on  your
backup strategy.

  **   If  you  use SAVLIB  LIB(*IBM),  you  would use  the  Q$$TAATOOL
       library  as  the Q  libraries  are saved  by  the  special value

  **   If you  use SAVLIB  LIB(*NONSYS), you  would use  the  $$TAATOOL
       library  as the  libraries are  saved  in straight  alphabetical

After  restoring the  SAVSYS media,  configuration, and  security data,
you  would mount the SAVLIB media and  call the TAASAVPC program in the
library you are using  (either $$TAATOOL or Q$$TAATOOL) to  restore the
TAATOOL  and   TAASECURE  libraries.    After   restoring  TAATOOL  and
TAASECURE,  the TAA Tool commands (such as  RSTALLLIB) can then be used
to install the remainder of the libraries.

If you  want to  use  the SAVTAATOOL  approach, see  the  documentation
about the tool.

Added to TAA Productivity tools April 1, 1995

Home Page Up to Top