HP 3000 Manuals

Information Access Server: Planning and Configuring

Worksheet 1:  PC Data Requirements 

PC Data Requirements 


          Figure 1-1.  Labeled Diagram of Configuration Worksheet 1 

Objective.   

The primary DBA or the secondary DBA uses this worksheet to gather
detailed information from PC users about their current data needs.

Worksheet Description.   

 At the top of the worksheet are spaces for the PC USER NAME
 (A), DBA capability (B), if any, and the DATE (C) the
 information was gathered.

          Table 1-0.  (cont.) 

                          The first six columns are labeled DATA REQUIRED FOR PC. They
                          indicate what data the PC user uses, some of the
                          characteristics of the data, and how frequently the PC user
                          needs it.

(D) APPLICATION           What PC application (if any) the data is used in.

(E) NAME OF DATA          The name of the data item.  (Take note of any limitations on
                          item names in applications your PC users routinely use.)

(F) TYP                   The type of information.  The worksheet suggests N for
                          numeric, AN for alphanumeric, and A for a more general ASCII
                          format.  Don't feel confined to this suggested code.  You're
                          free to devise a code more suited to your circumstances.

(G) MTD                   The method by which the data is introduced into the PC
                          application.  Is it a DIF file for use in VisiCalc?  Is it a
                          QB (Quoted Basic) file used in Lotus 1-2-3 or in R:base?  Or
                          is it an ASCII file used in a PC word processor?

(H) DESCRIPTION OF DATA   A place to expand on the information in previous columns or
                          to note anything unusual about the data item.

(I) FRQ                   The frequency of need for this data.  On the average, how
                          often does the PC user need this data?  Every day, each week,
                          once a month?  The frequency of the data need will help you
                          determine which PC users stand to benefit most from
                          Information Access.

                          The last seven columns are labeled DATA SOURCE. They indicate
                          where the PC user currently gets the required data.  For
                          IMAGE data, you can identify the system, database, and
                          dataset the data item resides in; for file data, indicate the
                          system and file name.

(J) CURRENT SOURCE OF     Where the user currently gets the data from.  The data source
DATA                      may be a utility the user runs, or a custom program, or the
                          user may be handed this information as a report generated by
                          a programmer.

(K) LOC                   The location of the data.  The worksheet suggests PC for
                          local PC data, H for data from the host HP 3000, and  R for
                          data from remote HP 3000s.  Feel free to modify this
                          suggested code to something more suited to your computing
                          environment.

(L) SYSTEM NAME           The name of the computer the data item resides on.  For
                          remote HP 3000s, be sure to include the device class name or
                          the node name.  The name can be qualified, if necessary, by
                          the domain and organization under which the system is
                          configured for MPE. You'll be using this information to
                          define the remote HP 3000 in the Information Access data
                          dictionary.

          Table 1-0.  (cont.) 

(M) DATABASE OR FILE      The name of the IMAGE database or file associated with the
                          data item.  For databases and files, you may also want to
                          include the MPE group and account.  For IMAGE databases, you
                          could include the user class through which this PC user is
                          allowed to view the data source.

(N) DATASET               The IMAGE dataset associated with the data item.  For files,
                          you already indicated the source in the previous column.

(O) DATA ITEM or FIELD    The name of the data item in the IMAGE dataset or in the
                          file.

(P) FMT                   The format of the data item or field.  Use this column to
                          note items whose data types will need to be converted for use
                          in Access Server.  You can also prevent yourself from
                          including items whose data types are not supported by Access
                          Server.

                          For files, note such things as starting offset, length, and
                          type.

To Plan for PC Data Needs:.   

   1.  Make enough copies of Worksheet 1 in Appendix A so that each PC
       user who accesses any kind of data, regardless of the source, will
       have a worksheet.

   2.  Distribute the worksheet to PC users.  Explain the kind of
       information you need and have them complete the worksheet.

       For HP 3000 data, your PC users may only be able to complete the
       first six columns.  In those cases, you'll need to fill in the
       remaining columns yourself.

   3.  Once Worksheet 1 is completed, meet with each PC user, or with
       groups of PC users if you know that particular sets of users have
       common data needs.  Review what each user has written and make
       changes or notes as needed.

       If you are a primary DBA and want to designate any users as
       secondary DBAs, put an X (or any other character) beside "DBA" on
       the form.  (This item is optional; you do not have to designate
       any secondary DBAs.)  You may want to evaluate all the users'
       needs before deciding on this item.  You could designate secondary
       DBAs who are not PC users.  For example, you might designate a
       member of the MIS programming staff to be a secondary DBA.

   4.  Provide copies of the completed worksheet for yourself and for the
       users.

   5.  Be sure to ask users about any foreseeable changes in their data
       needs as well.  Their job responsibilities may be changing soon,
       or they may be completing one major project and beginning another.
       Ask them to notify you whenever the information on Worksheet 1
       changes.

Once you've collected Worksheet 1 from your PC users, you'll have a good
idea which PC users should be configured as Information Access users or
secondary DBAs.  It will probably also be clear, because of their common
data needs, which users belong together in one access group.

Because you've determined the source of the data your PC users need,
you'll also have a good idea what data should be defined in Access
Server.  For instance, if you're using the Remote 3000 Link, you'll know
which remote systems, databases, files, and datasets need to be
configured for use in Access Server.

If your users plan to use Access PC output in their PC applications,
you'll need to be aware of any special formats or naming conventions the
data must conform to.  Here are some things to be on the lookout for:

   *   Is the maximum length of item names and table names used in the
       application less than the 16 characters allowed by Access Server?
       Are the naming conventions more restrictive?  If so, you need to
       configure your tables accordingly.

   *   What data types does the PC application support?  See Chapter 6,
       "Transferring Data Types," in the Information Access PC 
       Connections and Batch Files manual, for information about
       conversion of data types.

   *   If the PC application accepts real numbers, does it require the
       decimal point always to be in the same place?  If so, this
       requirement will affect how you configure your tables.

Your PC users will probably be able to alert you to these things for the
PC applications they use.  If not, consult the reference manuals for the
products in question.

MPE/iX 5.0 Documentation