Administrating
Dataquery

This section provides information about and procedures for performing
Datacom/DB
systems tasks.
datacom151
This section provides information about and procedures for performing
Datacom/DB
systems tasks, including:
  • Establishing the operating environment
  • Creating the system databases and areas
  • Maintaining the system databases and areas
  • Customizing the
    Datacom
    environment
  • Creating databases
  • Maintaining databases
  • Writing and interfacing exit programs
  • Monitoring system performance
  • Tuning system performance
  • Diagnosing and resolving system problems
This section is intended for
Dataquery
Administrators, systems programmers, and Database Administrators who are responsible for one or more of the following:
  • Installing
    Dataquery
    system software
  • Supporting
    Dataquery
    system software
  • Administering the operations of the
    Dataquery
    system
  • Maintaining data integrity
  • Ensuring data accessibility
  • Maintaining system performance
Dataquery
Administrator Role
To effectively administer the
Dataquery
system, you must have the following qualifications:
  • You must have a thorough knowledge of
    Datacom/DB
    and at least a general knowledge of the other
    Broadcom
    products that execute with
    Dataquery
    . You must be able to determine if problems that can arise are a result of
    Dataquery
    or
    Dataquery
    's interaction with one of these other products.
  • You must have a general knowledge of the operating system environment. You should know the CICS environment when
    Dataquery
    online operates under CICS.
  • You must have a general knowledge of
    Dataquery
    . Depending on the environment, you may either be actively involved in creating queries or may use
    Dataquery
    only when there are problems to be solved. You must understand
    Dataquery
    well enough to know how
    Dataquery
    impacts the operation of the
    Datacom/DB
    system and how to optimize
    Dataquery
    operation and the operation of
    Datacom/DB
    when
    Dataquery
    is being used.
    It is important that you know that:
    • Users can update databases if authorized.
    • A data authorized user can read any database.
    • A user cannot log on to more than one terminal with the same user ID and password.
Tasks
Dataquery
Administrators handle the day-to-day administration of
Dataquery
. Following are tasks for which a
Dataquery
Administrator can be responsible:
  • Modification and tailoring following
    Dataquery
    installation.
    • User Requirements Tables. See Defining the
      Dataquery
      User Requirements Tables.
    • Creating user signons/passwords and setting up authorizations.
    • DQSYSTBL (assemble
      Dataquery
      system table macro (DQOPTLST) and link edit using name DQSYSTBL).
    • Other
      Dataquery
      tasks contained in members that are available on the
      Datacom
      page on Broadcom Support. See the
      Datacom
      Release Notes
    • Programming user exits.
    • Implementing
      Dataquery
      security.
  • Maintenance after
    Dataquery
    is operational.
    • Supporting users and diagnosing problems.
    • Managing query and JCL libraries.
    • Performing backups and restores of
      Dataquery
      tables.
    • Using batch maintenance utilities.
    • Upgrading supporting products and implementing required changes following upgrades.
    • Modifying the batch
      Dataquery
      systems options table to meet site requirements.
    • Executing deferred batch queries.
    • Maintaining
      Dataquery
      system tables.
    • Loading and backing up
      Broadcom
      -supplied languages.
  • Monitoring and tuning
    Dataquery
    .
Responsibilities
As the
Dataquery
Administrator, you are responsible for ensuring that all the system tasks required for optimum
Dataquery
performance are performed. During use of
Dataquery
, you ensure that the system needs of the users are met and that the system maintenance includes the
Dataquery
needs. You tune
Dataquery
and
Datacom/DB
to improve or maintain the performance. To perform these tasks, you need to work with the Database Administrator, the systems programmer, the Security Administrator, the
Datacom Datadictionary
Administrator, and possibly the
Dataquery
users.
Your system responsibilities include:
  • Knowing the system defaults that affect end users.
  • Providing the Database Administrator with information about
    Dataquery
    end-user needs.
  • Being knowledgeable about
    Dataquery
    batch utilities.
  • Understanding the operation of any user exits designed at your site which affect the end user.
  • Knowing how to use
    Dataquery
    diagnostics and
    Datacom/DB
    accounting statistics in monitoring system and user performance.
  • Maintaining signon information.
Site Standards
Your site can have one
Dataquery
Administrator who performs all of the
Dataquery
administrative functions, or it could have several
Dataquery
Administrators among whom the tasks are divided, or performed for a particular group of users, such as an office with more than one department.
Required
Dataquery
Skills
Learn about
Dataquery
so that you can support your users. Also, you need to be fully authorized so that you can use all the
Dataquery
features if you need to. The following highlights those subjects that are of particular importance to you. You should know how to perform the following tasks:
  • Establish security.
    Choose the SECURITY CONTROL option from the Administrative Menu. With this panel you can:
    • Authorize users to access tables and perform the FIND, UPDATE, INSERT, or ERASE functions.
    • Authorize users to access columns protected by profile-codes.
  • Authorize a user.
    • Use the USERS option from the Administrative Menu.
    • Type USERS on the command line.
    With this you can add, delete, or maintain users.
  • Force a user to log off.
    Use the USERS option from the Administrative Menu. Use the PF key to display the Directory of Active Users. Use a PF key to FORCE OFF the active user.
  • Override predefined system defaults for a user.
    Use the USERS option on the Administrative Menu.
  • Use diagnostics.
    See Using DQL Diagnostics for details.
  • Get
    Dataquery
    statistics.
    See Using
    Datacom
    Core Statistics
    for details.
  • Create and modify JCL members for batch submission.
  • Maintain the Query Library Table (DQQ).
  • Perform online library maintenance with the online Administrator functions described in Accessing the Online Administrative Functions.
    You can use the DQLIBRMT utility to:
    • Delete all or selected members for selected users or groups
    • Back up all queries, dialogs, terms, JCL, and PROC members or selected members from the Query Library Table to tape or disk
    • Restore all or selected members to the Query Library Table from a tape or disk file
    • Print maintenance reports that:
      • List each user's query and type
      • Show selected user's query text or JCL
      • Show maintenance functions per query
      • List any errors that occur during query maintenance
  • Create and send a message.
    Use the USERS option from the Administrative Menu. Use the PF key to get to the Directory of Active Users. Then use the PF keys to do a CREATE MSG or a SEND MSG.
  • Broadcast a message.
    Dataquery
    displays a bulletin board immediately after a user signs on. The bulletin board can be used to distribute information to all
    Dataquery
    users. Select the LANGUAGE option on the Administrative Menu. For details, see Changing the Bulletin Board.
  • Cancel a user's query while it is processing.
    Use the USERS option from the Administrative Menu. Use the PF key to get to the Directory of Active Users. Then use the PF key to do a CANCEL FIND.
  • Use the Printer Control option on the Administrative Menu. For details, see Using the Printer Control.
  • Disallow use of a query.
    If a query is being used that is causing system problems, you can use the
    Dataquery
    Administrator Library Maintenance function to change the author's name to an unknown author and make the query private. This keeps the query from appearing in the user's library. This does not delete the query but keeps it from being used until the problem is resolved.