/**************************************************************************/
/* IBM P/370 & P/390        (c) Copyright IBM Corporation 1988, 1998      */
/*   Configurator Help Messages            Release 4.20     3/18/98       */
/**************************************************************************/
    This is the Configurator help messages file. It is a human readable and
easily edited file. The only rules for use are these:

    The Configurator has a help function key for each of the menus that can
appear on the screen. When F1 is pressed, the help function scans this file
for a header record that contains a key word signifying the beginning of a
help message group. Usually, the keyword is the name of the function menu
that appears on the bottom right hand of the screen when any menu is being
displayed by the Configurator. The header record contains that name and
nothing else.

    After the header record, up to 1050 lines can be typed for each help group.
Each line can be a max of 79 bytes. Lines longer than 79 bytes could cause
strange things to appear on the screen. Any information past 1050 lines will
not be processed and therefore will not be shown on the screen.

    After the LAST line of the group, the NEXT line MUST contain the 2 chars
"<>". This is how the program senses the end of the help group. This is
done to facilitate the paging functions of the help system.

    All records that are outside of any help group are ignored as this top
section description will also be ignored.

    Since this file can be edited by any general purpose editor, you can
change these help messages without having to change the program itself.
/*------------------------------------------------------------------------*/
/*  help for the password entry, the first menu to appear                 */
/*-------------------------------------------------------------------------*/
conpaswi
This menu handles the Configurator password and the names of various files
needed by the Configurator.  If you have never changed the password, then the
default password is "SYSTEM".  If the password is SYSTEM, then you can simply
press ENTER to continue.  Otherwise, you MUST type in the password and then
press ENTER.  The letters of the password will NOT appear as you type them.

Three of the filenames at the top right are stored in the DEVMAP file.  The
DEVMAP file name is a protected "display only" field.  You can type over the
other file names if you need to change them.  If any errors occur, a message
window will appear.  After correcting the errors press ENTER to continue.

If you are NOT running VM (or you are not using the Configurator to maintain
the VM user directory) then the DIRECTORY field should be set to all blanks.
The "Update User Data" menus will be disabled.

If you are running in a mode that does not require the DMKRIO.ASM file (e.g.
VM/ESA 2.2 or a non-VM operating system), then this field should also be
blanked out. If the DMKRIO.ASM field is empty, then the UPDATE SYSTEM DEVICES
frame will be in a mode which will require you to specify the device type for
new device allocations. If DMKRIO.ASM is present, this is done automatically
and the device address is also checked for accuracy.

The DEVMAP file that the Configurator will use is normally set by the AWSPROF
program. The DEVMAP that AWSPROF sets is important as this is the DEVMAP that
both the Configurator and the P/390 system use as defaults. You can, however,
change the DEVMAP that the Configurator works with by invoking the program
directly from the OS/2 command line:

             AWSCFG devmap_name

where an optional parameter specifies the fully-qualified OS/2 filename for
the DEVMAP which you wish to use.  Any valid filename up to 30 characters may
be supplied.  If this parameter is not used, then the default filename is
"DEVMAP.1VM" from the current directory where you are invoking the program.

There are other command line options available.  To see a list of them and
their syntax, start the Configurator using the '?' parameter:

             AWSCFG ?

The DEVMAP file contains special Device Mapping information that is used by
the P/390 device managers.  It MUST be present to run the P/390.  It is NOT
readable and it should NEVER be edited using an OS/2 text editor.  The
Configurator handles all of the updating and editing of this file.

If you are running VM/ESA (370 feature) or an earlier VM/SP release, then
the DMKRIO.ASM file supplies the Configurator with information about the Real
I/O (RIO) devices which are defined to VM.  It is readable and can be edited
using an editor, but note that any changes which are made to this file will
have NO effect on the Real I/O configuration of the P/390.  You should contact
your VM System Programmer for any modifications that you may need in this
file.  The Configurator only reads this file and does not modify it in any way.
If the field is left blank, you will be required to supply the device types
See the appropriate VM guide for more information about DMKRIO.

The USER.DIR (user directory) file is used by the VM control program in the
P/390 to describe Userid's, user minidisks, and other virtual machine
information.  The file does NOT have to be present for the Configurator to run,
but those menus that operate on the directory will NOT be operational if this
field is blanked out at startup time.  This file can be read and changed using
an editor, but modification of this file is STRONGLY discouraged because the
Configurator must sometimes reflect certain modifications in both USER.DIR and
DEVMAP.  In practically all cases, the editing features of the Configurator
will allow you to change all aspects of the directory without having to edit
the file directly.
<>
/*----------------------------------------------------------------------*/
/* help for the FUNCTIONS main menu                                     */
/*----------------------------------------------------------------------*/
cnfuns
This is the MAIN MENU.  It has 9 functions in addition to this help function
you are reading now.  A short description of each function follows.  The
functions that have their own menus will be further described in the help
section of those menus.

   F1 - Help

   Help is always available by pressing the F1 key on any menu.

   F2 - Update System Devices

   This menu is a formatted display of the device information which is
   contained in the DEVMAP file.  It deals exclusively with real I/O devices,
   and is mostly for use by a system programmer.

   F3 - Update User Data

   The USER DATA is the information contained in the USER.DIR or VM directory
   file.  Use this menu to add, change, or delete Userid's and minidisks.

   F4 - Update System Environment

   Use this menu to update system environment data such as the IPL address,
   IML mode, LAN NetID, GMT time-of-day offset, etc.

   F5 - Update Configurator Password

   Allows the user to change the password for the Configurator.

   F6 - END - SAVE ALL UPDATES

   This is the normal way of exiting the Configurator. Ending this way
   over-writes the DEVMAP and (if used) the USER directory file.

   If you make a mistake while making your changes, DO NOT choose this form of
   exit, but rather use the F10 key (described below).

   F7 - Update 3270 LT Sessions

   This menu allows you to define how the 3270 Logical Terminal sessions are
   allocated. They can be defined as Local P/390, Host coax, or LAN P/390.

   F8 - Save-all, do not end program.

   Using this key will do the same operation as in F6 above, except that you
   will stay in the main menu frame and not have to startup the entire
   program to continue and make more changes.

   F9 - Display Files Not Found.

   If there are OS/2 files (containing minidisks) which have entries in DEVMAP,
   but cannot be located when the Configurator is started, then you will see a
   message at the bottom of the FUNCTIONS menu:
      "NOTE: DEVMAP references files not found on the system."
   You may use the F9 key to display the names of these missing files.

   F10 - QUIT - DO NOT SAVE ANYTHING

   Use this key to exit the Configurator without saving ANY changes that you
   have made since you entered the Configurator. Note that any OS/2 files which
   are allocated or deleted are unaffected by which exit you take (F10 or F6).
   Thus, if you use F10 to QUIT, you may have created OS/2 minidisk files which
   do not have a DEVMAP entry, or you may have deleted an OS/2 file and yet
   still have a DEVMAP entry for the file.  You will be asked to confirm this
   exit if any changes have been made.

   F11 - Configure 3172 SDLC Gateway

   This menu lets you run the 3172 SDLC SNA configurator program.
<>
/*----------------------------------------------------------------------*/
/* help for the change password menu                                    */
/*----------------------------------------------------------------------*/
conpaswu
This menu allows you to change the Configurator password.  The password can
consist of any combination of normal numbers and letters.  The letters will be
converted to upper case.  The new password WILL appear as you type it.  Both
the new and old passwords are displayed at the same time so you can compare
them.  You must press ENTER for the new password to take effect, otherwise the
old password will still be valid.

The password is stored in an encrypted form in the DEVMAP file, and different
DEVMAP files can have different passwords, so be careful not to forget what it
was changed to.  The password is only written out when you exit and save all
changes made.
<>
/*----------------------------------------------------------------------*/
/* Help for ENVIRONMENT menu                                            */
/*----------------------------------------------------------------------*/
cnsysenv
This menu allows you to update the system environment data that controls the
P/390. The system data items which can be changed are listed, one per
line, each with an entry field at the right, beginning with the arrow head (>).
The current values are displayed in the fields.  To change any value, place the
cursor at the start of any field (using the TAB or arrow keys), type over the
current value with the new data, and then press ENTER or F10. Enter simply
reads the screen and does error checking for the various fields. F10 does the
same, except if there were no errors detected, it places you back at the
main menu. If errors were detected in either case, a message will describe
the error and you are given the opportunity to change the incorrect field.

The following system environment data can be changed:

  - Customer Name
    This forty character field will appear in P/390 dumps.

  - Local Area Network NetID
    This specifies the LAN name identification for your P/390. It is the
    NetBios node name that is used by other P/390s and client PCs to connect
    to your P/390. It must be a UNIQUE name of 8 alphanumeric characters or
    less. You should make this name match the system node ID of your P/390.

  - System IPL address.
    This specifies the real address of the system IPL volume.  It must be
    three hexadecimal digits.  The default = "300".

  - System IPL PARM.
    An IPL parameter that gets passed into the P/390 operating system.  The
    meaning and use of this parameter is system dependent. In VM/ESA, for
    example, a PARM of 0200 would display the SALIPL screen on terminal
    address 200.  This field can contain up to 8 characters.

  - System GMT offset.

    This specifies the offset from Greenwich Mean Time that is used to set the
    system clock in the P/390 processor. Its format is:
                          HH:MM W|E (West or East)
    Where:
           'HH' is a 2 digit hour offset
           'MM' is a 2 digit minute offset
            'W' is West of the meridian or a + offset
            'E' is East of the meridian or a - offset
       Leading zeros must be included for both HH and MM.
       If the W|E field is blank, it defaults to W.
       The colon is automatic, you do not need to type this in.

  - System CPUID.
    This is the CPU identification code for your P/390 processor. It must be
    6 hexadecimal digits.

  - Cache Size  - Valid only in 370 mode.
    This specifies the amount of processor main memory (in megabytes)
    to use for the CMS minidisk cache. If non-zero, this will decrease
    your P/390 processor's real storage by that amount.
    It must be a single decimal digit from 0 to 8.

  - Expanded Store Size (nn)
    This specifies the amount of memory (in MBytes) to use as expanded store.
    The memory may be taken from either:
        "A"  The P/390 Adapter's memory
        "P"  The PC's memory (not supported on Microchannel PCs)
             For this option, you must also specify /X=nn on AWS370DD.SYS.
    Specifying a non-zero number will decrease either S/390 main memory or
    OS/2 memory by that amount.

    NOTE:- The total amount of cache and expanded store allocated can never
           be greater than one half the total amount of P/390 memory available.
         - If you use PC memory, be sure to leave at least 32MB for OS/2.
         - If the amount of PC memory requested is greater than /X=nn parameter
           specified in CONFIG.SYS, then no expanded storage is allocated.

  - Character font name.
    This specifies the name of the font which will be used for all 3215
    sessions (for example, an Operator's console).
    The following fonts are available on most PCs:
      12.System Monospaced
      10.System Monospaced
      12.Courier
      10.Courier
       8.Courier
    The names must be typed in EXACTLY as shown.
    To use the default standard font, enter spaces into this field.

For any changes to take effect, you must select "F6 END - SAVE ALL UPDATES"
from the FUNCTIONS main menu when you exit the Configurator.  This data is
stored in the DEVMAP file.
<>
/*-----------------------------------------------------------------------*/
/* the SELECT USERID menu for the directory edit                         */
/*-----------------------------------------------------------------------*/
cnusers
This is the first menu involved with editing the USER.DIR directory file.  The
userids listed in the main display area of this menu are those which were found
in your directory.

There are three types of userids in this list:

      General Userids - sorted and displayed in YELLOW
      Userids reserved for System Functions - displayed in DARK BLUE
      System Directory Profiles - displayed in LIGHT BLUE and at bottom of list

You can select one of these userids for deletion or modification.  You can also
add a new USERID or a PROFILE to the directory.

1. To SELECT a userid for modification or deletion, place the cursor anywhere
   under the userid name and press ENTER or F3.  The USER FUNCTION SELECTION
   menu will then appear.

2. To DELETE a userid from the directory, place the cursor anywhere under the
   userid name and press F9.  The name will be highlighted in "reverse video"
   signifying that the entire group of records associated with that name will
   be deleted when you exit the Configurator with "F6 END - SAVE ALL UPDATES".
   If you use F8 (save, do not end) and you come back to this frame, those
   entries that were marked for deletion will still be highlighted.

3. To UNDELETE a userid, place the cursor back under the name and press F5 to
   restore the userid and all of its data.  When any name is marked for
   deletion, you cannot do any operations on that userid, but the data
   associated with that userid is retained until you exit the Configurator in
   case you want to undelete it.

4. To ADD a new userid to the directory, use the TAB key to place the cursor
   into the NEW USERID field.  (Shift-Tab will get there the fastest).  Type
   in a name up to 8 characters and press ENTER.  You will then be placed into
   the USER ENVIRONMENT menu where you can then describe the logon password,
   virtual storage sizes and other information.

5. To ADD a new PROFILE to the directory, use the TAB key to place the cursor
   into the NEW USERID field.  Type in a name up to 8 characters and press F12.

6. To copy an existing userid to a new userid, place the cursor under the name
   and press F11. The existing user name will turn red and the cursor will move
   down to the new userid entry field. Type in a new user name and press ENTER.
   You will be placed into the USER ENVIRONMENT menu where you must provide
   a logon password because the original password is NOT copied. Next, go to
   the USER MINIDISK menu and note that new minidisk files must be allocated.
<>
/*-------------------------------------------------------------------------*/
/* USER FUNCTION SELECTION menu help                                       */
/*-------------------------------------------------------------------------*/
cnuserfu
From this menu you can select one of the three main groups of directory
statements which you can modify.  Press the appropriate function key to bring
up the corresponding menu:

   F2 - User Environment

   This menu allows you to define the all of the virtual machine's environment
   EXCEPT the LINK and MDISK statements.

   F3 - User Minidisks

   This menu is used to add, delete, or change this Userid's minidisks.  It
   modifies the MDISK statements in the directory and allocates or deletes the
   OS/2 files associated with those minidisks.  It also automatically updates
   the DEVMAP file with DASD entries for each allocated minidisk.

   F4 - User Links

   This menu is used to add, delete, or change LINKs to other user's minidisks.

You can select another userid without returning to the USER SELECT menu:
   F7/Page Up - Scroll back one user.
   F8/Page Down - Scroll forward one user.

   F10 - Takes you back to the FUNCTIONS main menu.

   ESC - Takes you back to the USER SELECT menu.
<>
/*------------------------------------------------------------------------*/
/*  user USER ENVIRONMENT menu help                                       */
/*------------------------------------------------------------------------*/
cnuseren
This menu allows editing of ALL statements in the directory EXCEPT the MDISK
and user LINK statements.  These have their own menus.  For descriptions of all
directory statements, please consult the "VM/ESA Planning and Administration
Guide" for more information.

The display has two main areas of interaction.  The top line of the large
display area has fields that describe information that is contained in the
"USER" directory statement.  Below that is the large fullscreen editing area
where all of the other statements can be edited on a line at a time basis.  No
syntax checking is done.

At the very top of the screen (in the title area) the userid name that you are
working on can be changed.  This is the only place where you can rename the
userid name.  Place the cursor in that field and type over the name that is
already there.  Press ENTER to make the change in the system.


1. The USER fields:

   Logon Password>
   This the logon password that must be used when you logon to this userid on
   the P/390.  It consists of 1 to 8 characters or numbers.  To change it, type
   over the existing password and press ENTER.  For NEW Userids this field will
   show "********" indicating that you MUST type in a new password.  Make sure
   you blank out the remaining *'s  if your password is less than 8 characters.

   Logon Storage>
   This is the virtual storage size that you get when you first log on to this
   userid.  It is expressed as 1 to 4 decimal digits followed by either "K" for
   Kilobytes, or "M" for Megabytes, e.g. "1M" or "1024K".  In VM/ESA (ESA
   feature) only "M" is allowed.  To change it, type over the existing data
   and press ENTER.

   Maximum Storage>
   This is the maximum virtual storage which you can define after you have
   logged on.  To change it, type over the existing data and press ENTER.

   User Class>
   This field can contain up to eight user privilege classes.  The available
   classes will be specified by your System Programmer.  Normally, you will
   specify class "G" (general user). In VM/ESA (370 Feature) this field can
   also contain any other options that normally follow the user class option.
   Specify these options by separating the user class value with a blank and
   then typing in the rest of the options. The max number of characters for
   BOTH the userclass and any other options is 23.

2. The Main Editing Display area.

There may or may not be any data displayed here depending on what was found in
the directory.  For NEW Userids the first line will be a comment containing a
timestamp.  We recommend that you place an INCLUDE USERPROF statement, if
appropriate, as the first statement.

You can add, delete, or change statements by pressing the
appropriate keys, as described below:

   Line by line input

   Place the cursor anywhere in the main editing area and start typing. You
   can type in a free form manner, line by line, using the cursor keys to
   move to the next line. When any function key is pressed (including ENTER)
   the data is read in and you can go on and do more.

   F6 - INSERT

   To INSERT a line into the main display area, place the cursor on an existing
   line UNDER which you wish to insert.  Press F6 and the other lines in the
   display will be moved down and a space will open up below the cursor.  The
   first column will initially contain an "*" (indicating a comment).  If you
   are entering a directory statement, overtype the "*" and type in the new
   data. All non-comment data will converted to upper case.

   F9 - DELETE

   To DELETE a line, place the cursor UNDER the line to be deleted and press
   F9.  The line will be replaced by the line below and all lines will move up
   one position. Remember that once a line is deleted, there is no way to get
   it back unless you "QUIT" out of the Configurator without saving ANY data.
   (There is NO undelete function on this menu).


Other Function Keys are:

    F2  - Return to the USER FUNCTION SELECTION menu.

    F3  - Go to the UPDATE USER MINIDISKS menu.

    F4  - Go to the UPDATE USER LINKS menu.

    F7/Page Up   - Scroll backwards.  Either key may be used.

    F8/Page Down - Scroll forwards.   Either key may be used.

    F10 - Return to the FUNCTIONS main menu.

    ESC - Return to the USER FUNCTION SELECTION menu, discarding all changes
          made since the last ENTER or function key operation.
<>
/*----------------------------------------------------------------------*/
/* UPDATE USER MINIDISK help menu                                       */
/*----------------------------------------------------------------------*/
cnuserud
This menu allows you to manipulate minidisks for a particular user.  Changes
made on this menu affect the MDISK statements in the USER.DIR file.  You can
allocate, change, or delete minidisks from this menu.

The menu has two main areas of interaction:  At the top of the main display
area is a line of input fields, each beginning with an arrow head (>).  Use
this line when you want to allocate a new minidisk for this user.  The middle
of the display shows the existing minidisk entries.  You can change this data
by moving the cursor to the unprotected entry fields (using the TAB or arrow
keys), typing over the existing data, and then press ENTER.

1. To ALLOCATE a NEW minidisk, fill in these fields:

 VIRTUAL ADDRESS: The 3-4 digit hexadecimal address that you want the minidisk
                  to have under P/390 VM for this userid. This is a required
                  entry. The address must be unique within this virtual
                  machine.

 DASD TYPE:       This is the device type of the DASD that the minidisk is
                  emulating. The default, if left blank, is FB-512.

 CP VOLUME LABEL: A UNIQUE six character alphanumeric label for this disk
                  volume.  It cannot be duplicated anywhere within the
                  P/390 system. This entry is required.

     ACCESS MODE: An optional one or two character access mode. If left blank
                  it defaults to "MR" (Read/Write access).

       FILE SIZE: The size of the minidisk in Kilobytes (1024 bytes),
                  Megabytes (1024 KB), or 512 byte Blocks.  For Count Key Data
                  DASD you can also specify Cylinders.  Use a decimal number
                  followed by EITHER a K, M, B, or C.

        FILENAME: The name of the OS/2 file to be allocated as a minidisk.
                  It is of the form:
                                     d:\path\name.ext
                  If you specify only the 'name.ext' portion, then the drive
                  letter 'd:'  and subdirectory 'path' will be taken from the
                  "Path >" field displayed after the "FILENAME" header.  If a
                  different drive is specified but no subdirectory is given,
                  then the current subdirectory on that drive will be used.

                  You can also type in any valid OS/2 drive and subdirectory.

                  If the filename field is left BLANK, then the system will
                  generate a filename for you of the form:
                              PATH\USERID.VIRTADD
                  This follows the convention for P/390 user minidisk files,
                  but is not required. You must, however, specify both a file
                  name and file extention if you do not want the default name.
                  NOTE: if the virtual address has four characters, this
                  feature is not activated. You must supply the filename.

   After the data has been typed in, press ENTER to allocate the new minidisk.
   If the allocation is successful, the entry line will be moved down into the
   main display area.  A MDISK entry will be added to the USER.DIR file and a
   new device entry created in DEVMAP.  For these changes to take effect, you
   must select "F6 END - SAVE ALL UPDATES" from the FUNCTIONS main menu when
   you exit the Configurator.  After you IPL the P/390 and log on to this
   USERID you must use the CMS "FORMAT" command before you can use this
   minidisk. See the "VM/ESA CMS Command Reference" for details.

2. To CHANGE an EXISTING minidisk entry:
   Move the cursor to any of the unprotected entry fields in the main display
   area and type over the data which you wish to change, and then press ENTER
   for the changes to take effect.  The main display area may be scrolled to
   display additional minidisk entries. Page Down or Page UP scroll one full
   screen at a time. F7(back) and F8(forward) scroll on a line by line basis.

   At the bottom of the main display area is window that displays the complete
   MDISK card as it currently exists. Fields that are not frequently changed
   can be updated here. These include the START, EXTENT, and PASSWORD fields.
   As you move the cursor in the main display area under any part of an entry,
   the corresponding MDISK card will be displayed in the lower box.
   To change specific information on the MDISK card, press ALT+F5. Those
   fields that can be changed will become unprotected and RED in color and will
   also have a ">" in front of each variable field. Make the changes needed
   and press ENTER to accept the new data. These fields are:

   START        : The distance from the begining of the MINIDISK where the
                  volume will begin. It is specified in 512 byte blocks (for
                  FBA DASD) or cylinders (for CKD DASD). User minidisks will
                  usually start at block 16 or cylinder 1.

   EXTENT       : The size of the MINIDISK itself. It is specified in 512
                  byte blocks (for FBA DASD) or cylinders (for CKD DASD).

   READ PASSWORD: An optional 1 to 8 character password. If left blank it
                  defaults to "ALL" (unprotected).  A READ password is required
                  if you specify a WRITE or MULTIWRITE password.  The READ
                  password lets other users share your disk in R/O mode.

  WRITE PASSWORD: An optional 1 to 8 character password. A WRITE password is
                  required if you specify a MULTIWRITE password.  The WRITE
                  password lets other users access your disk in Write mode.

  MULTIPLE WRITE: An optional 1 to 8 character password.  It is the password
                  that lets other users gain Multi-Write access to the disk.

3. If the Virtual Address is highlighted in "reverse video", this means there
   is some error in the minidisk entry.  Move the cursor down under the
   highlighted address and a description of the error will be displayed with
   instructions on how to fix the error.  If the virtual address that is
   highlighted is NOT a normal user minidisk, but rather a VM/ESA system
   volume, BEWARE!  Do NOT try to fix them unless you know what you are
   doing!! Some system volumes have multiple extents or other non-minidisk
   like attributes that will cause them to be highlighted when there is no
   real error.

   Most of the "System" userids (those beginning and ending with "$" signs)
   will have apparent errors in the minidisk extents; you can ignore these
   since they are not real userids.  Also, any OS/2 file that contains more
   than one minidisk extent will be highlighted. Do not attempt to correct
   these with the Configurator!

4. To DELETE a minidisk entry statement from your directory:
   Place the cursor under the Virtual Address field of the disk that you want
   to delete and press F9.  The line will be highlighted and you will be asked
   to confirm the deletion by pressing F9 again. If there is an OS/2 file
   associated with this entry (the FILENAME field is not blank) then you will
   be asked whether you want to also delete the OS/2 file that holds the
   minidisk.  If you press F9 again, the OS/2 file will be deleted
   IMMEDIATELY.  The minidisk entry will will not be deleted from USER.DIR
   until you select "F6 END - SAVE ALL UPDATES" from the FUNCTIONS main menu
   when you exit the Configurator.

5. To ALLOCATE an OS/2 file for an existing minidisk entry:
   If a minidisk entry has no File Size or Filename information, this means
   that there is no real minidisk file on your PC disk.  You can allocate a
   new minidisk using the information already provided in the minidisk entry.
   Move the cursor under the line containing the minidisk entry and press F11.
   The line will be REMOVED from the main display area and placed into the data
   entry line at the top.  You should complete or correct all required
   information and then press ENTER to allocate the file.  If the allocation is
   successful, the entry line will be moved back into the main display area.

6. To ADD a minidisk entry statement for an existing OS/2 file:
   Follow the instructions for "1. ALLOCATE a NEW minidisk", above, except:
    - Type the full OS/2 filename for the existing file, and press ENTER.
   You should see the message:
     "The filename specified already exists. Cannot allocate as a new file."
     "Press ENTER to update DEVMAP and the MDISK card for this entry or ESC..."
   Follow the instructions completely.  If it is successful, the entry line
   will be moved back into the main display area, and the correct Volume Label
   and File Size will be displayed.

7. Automatic Search for Existing Minidisk Files:
   This function handles the special case where the minidisk file exists on
   your PC fixed disk, and the minidisk entry also exists in USER.DIR. This
   could occur if you are installing a VM program product or set of minidisks
   that provides both the OS/2 files and updates for the VM directory.  If the
   minidisk file names obey the naming convention "userid.vaddr", then the
   search function can be invoked to add a DEVMAP entry for each minidisk file
   that has a corresponding MDISK statement. Only those entries that have
   virtual addresses of three characters will be used in the search.

   Press ALT+F11.  The Configurator will search the PC drive and subdirectory
   indicated by the "Path >" field for the missing minidisks (indicated by a
   blank file size and blank file name).  If any disks are found, it will fill
   in the missing information.  If any errors were detected along the way, you
   are given the opportunity to fix the error or cancel the operation for that
   one entry.

8. TDISKS
   You can specify a special type of MDISK entry known as a T-DISK or
   temporary disk. The space for this disk actually comes from the system
   TDISK as defined in the SYSTEM UPDATE DEVICES frame (F2). Since no real
   file is allocated for this volume, and no entry is made in the DEVMAP, it
   is specified in a special way. To create a temporary disk, type on the new
   entry line a Virtual Address, Size, and for the File Name enter "T-DISK".
   The other fields are not used and will default.  To change the size of a
   T-DISK, delete the entry and create a new one.


The Function keys are:

    ALT+F1 - Display a list of the valid function keys.

    F2  - Go to the USER ENVIRONMENT menu.

    F3  - Return to the USER FUNCTION SELECTION menu.

    F4  - Go to the USER LINKS menu.

    F7/Page Up - Scroll backwards line or page.

    F8/Page Down - Scroll forwards line or page.

    F9  - Delete minidisk entry.

    F10 - Return to the FUNCTIONS main menu.

    F11 - Allocate an OS/2 file for this minidisk.

    F12 - Return to the SELECT USERID menu.

    ALT+F5   - Change start, extent and password fields on MDISK card.

    ALT+F11  - Search for existing OS/2 minidisk files in current directory.

    ESC - Return to the USER FUNCTION SELECTION menu, discarding all changes
          made since the last ENTER or function key operation.
<>
/*-----------------------------------------------------------------------*/
/* LINK LIST for user help                                               */
/*-----------------------------------------------------------------------*/
cnuserlk
 This menu allows you to add, delete, or change the LINK statements in the
 directory for this userid.  The main display area consists of 15 scrollable
 lines with 4 fields for each line.  The data entered in these fields is used
 to produce the LINK statements when the new directory is written out.

There are two modes of operation:
   -  Change existing data by typing over the displayed data.
   -  Use the function keys to insert new lines and delete lines.

To CHANGE existing data, use the TAB or arrow keys to position the cursor in
the desired field, type over the data on the screen, and press ENTER to save
your changes.

The four fields in the main display area are:

      USERID  - The userid who owns the disk to which you want to link.
      VIRTAD1 - His disk's virtual address
      VIRTAD2 - Your virtual address that will be used to access his disk.
         MODE - The access mode for the linked disk.  Consult the "VM/ESA CP
                Command Reference" (LINK command) for more information on
                the different types of link modes you can specify.

   If you leave the MODE blank, it will default to "RR" (Read/Only access).
   Any errors or conflicts with existing virtual addresses will be flagged.

The function keys are:

     F2 - Go to the UPDATE USER ENVIRONMENT menu.

     F3 - Go to the UPDATE MINIDISKS menu.

     F4 - Return to the USER FUNCTION SELECTION menu.

     F6 - Add a line to the display area just below the line where the cursor
          is placed. After you type data on the new line you MUST press ENTER
          to keep the data. You can press F6 multiple times to insert more
          than one line.

     F7/Page Up - Scroll backwards.  Either key may be used.

     F8/Page Down - Scroll forwards.  Either key may be used.

     F9 - Delete the line containing the cursor. There is no provision for
          "undeleting" a line, besides quitting the Configurator without saving
          ANYTHING.

    F10 - Return to the FUNCTIONS main menu.

    ESC - Return to the USER FUNCTION SELECTION menu, discarding all changes
          made since the last ENTER or function key operation.
<>
/*----------------------------------------------------------------------*/
/* the UPDATE SYSTEM DEVICES help                                       */
/*----------------------------------------------------------------------*/
cnsysdev
This menu allows you to update the "P/390 I/O device" to "PC device" mapping.
This information is kept in the DEVMAP file. The UPDATE SYSTEM DEVICES menu is
essentially a complete display of the contents of the DEVMAP file, with limited
editing capabilities.  It allows experienced users to maintain the real I/O
device configuration of their P/390.

The menu has two main areas of interaction:

 - At the top of the main display area is a line of input fields, each begins
   with an arrow head (>).  Use this line when you want to add a new device.
 - The middle of the display shows the existing device entries which were
   found in the DEVMAP file.  This display may be scrolled to display
   additional entries with the function keys described below.

HEADER DEFINITIONS

     ADDR: the real device address. 3 or 4 hexadecimal digits.

   DEVICE: the device type at this address. If DMKRIO.ASM is present, this is
           taken from that file, otherwise, you must supply the device type.
      For example:
           3370/3310/0671/9332/9335/9336/FB-512 = FBA DASD volume
           3330/3350/3375/3380/3390/9345 = CKD DASD volume
           3278/3215 = display terminal
           1403 = system printer
           2540 = card reader
           3088 = Transparent File Access (HLINK command) or
                  Local Area Network (LAN3088) connection or
                  3172 addresses.
           2703 = Asynchronous communications port
           ICA  = SDLC port
           3420/3422 = Tape drive emulated on disk(ette)
           3422 = Optical Media Attach/2 emulation (OMA)
           3480/3420 = SCSI-attached tape drives
           9346 = 1/4 inch IBM SCSI tape drive
           PCSE or 3278 = PCSERVER path to OS/2 (PCOPY & OS2 commands)
           HFGD = 5080 graphics display

    LABEL: Volume Label for DASD. 6 characters.

    ATYPE: Allocation type. It is only required on entry for DASD.
      For example:
           PERM, TDSK, TEMP, PAGE, DRCT, DUMP, OVRD are valid for VM 370.
           PERM, TDSK, SPOL, PAGE, DRCT, PARM are valid for VM/ESA 2.1 & above.
           CMS means the minidisk does not have a CP label.
           CKD is a Count Key Data DASD device. The allocation type is not read
           VSE is a VSE-type volume label.
           INVLD means the file is not a recognized system volume.
           ???? means an unknown type of volume, but it is valid.
           DSPY for displays
           PRTR for printer
           blank for all others

     SIZE: File size in (K or M) bytes or Cylinders (C) for CKD DASD.
           Fullpack DASD may be allocated by specifying nD where 'n' is the
           column number in the table AWSCFULL.PAK. See header of that file
           for more information. For example, 2D for 3380 = 1770 cyls.

           FBA DASD may also be displayed in 512 byte Blocks (B) by pressing
           ALT+B to toggle between K and B.

      MGR: Code that identifies which P/390 device manager controls the device.
           See the list of MGR Codes at the bottom of the screen.
           The manager name will be displayed in one of three colors:
            - Yellow = manager has devices assigned to it.
            - Cyan  = manager has no devices assigned to it.
            - Dark blue = all devices are temporarily excluded for the manager.
           It is a required entry field although if left blank, it will default
           based on entries in the AWSCTYPE.MGR file.

     FN/P: File Name / Parameters. May be either:
           - OS/2 drive, subdirectory, & name.ext for DASD, disk-emulated tape,
             or a printer redirected to an OS/2 file.
           - P/390 session titles for displays,
           - 3088 Remote Name for LAN3088 devices,
           - optional parameters (or comments) as defined by the MGR type.
             To see if parameters are accepted, place cursor under an existing
             device line or a MGR name and press F1.


The Function Keys are:

   ALT+F1 - Quick help on Function Keys

   F1  - Device Manager Help
         Place cursor on an existing device address or under the manager
         name in the "MGR Codes" list at the bottom of the screen. Press
         F1 to display the appropriate .DOC file which gives you important
         details about configuring devices for this control unit type.

   F5  - Locate a device in DEVMAP. Type in the device's address in the ADDR
         field or a DASD volid in the LABEL field and press F5. If the device
         exists in DEVMAP, the screen will scroll to that address and
         highlight the address (reverse video).

   F7/Page Up - Scroll backwards.  F7 scrolls by line, Page is by screen.

   F8/Page Down - Scroll forwards.  F8 scrolls by line, Page is by screen.

   F9  - Delete a device entry (see below, "Manipulating Existing Devices")

   F10 - Return to the FUNCTIONS main menu.

   ESC - Same as F10, except any changes made without pressing ENTER or a
         function key are discarded.

   F11 - Allocate a DASD file (see below, "Manipulating Existing Device")

   F12 - Display/Edit Device Manager parameters

   ALT+B - Display DASD sizes in number of 512 byte blocks (nnnnnnB).
           Pressing this key again restores the normal file size representation

   ALT+R - Marks a DASD volume as Read/Only. A lowercase "r" will be displayed
           in front of the OS/2 filename. Pressing this key again removes the
           "r" and marks the volume as Read/Write.

   ALT+F2 - Change the volume name of a DASD entry. The cursor must be under
            the LABEL field when this key combination is pressed.

   ALT+F3 - Turns off (excludes) a range of devices. Excluded devices are
            displayed in dark blue.

   ALT+F5 - Turns on a previously excluded range of devices.

   Cursor control keys:
      TAB     = Move cursor ahead one input field.
      SHIFTAB = Move cursor back one input field.
      END     = Move cursor to end of input field.
      HOME    = Move cursor to FIRST input field.
      CTL+HOME= Display the FIRST frame of data
      CTL+END = Display the LAST frame of data

   Top entry line retrieve keys:
      CTL+up_arrow   = Retrieve previously entered data (backwards)
      CTL+down_arrow = Retrieve previously entered data (forwards)


ALLOCATING NEW DEVICES

You can add new DASD, display, printer, or other special devices to DEVMAP by
using the new device input fields located on the top line of the main display
area.  Each field begins with an arrow head (>).  If DMKRIO.ASM is present,
the devices that can be added at a particular address is determined by the
DMKRIO.ASM file. If that file is not present, you must always type in the
device type.

There are three modes of operation for new devices:

1. ADD a non-DASD device:
   Move the cursor to the first entry field (the ">" underneath the "Addr"
   heading), type in the real address of the device to be added, and press
   ENTER.  A new device record will be added to the main display area at the
   chosen real address, using the device type information contained in
   DMKRIO.ASM.  If DMKRIO.ASM is not present, you must also type in the
   device type.

   The control unit manager code is chosen based on defaults found in file
   AWSCTYPE.MGR.  If you wish to override the default, delete the device and
   add it again, this time specifying the desired MGR code from the list at the
   bottom of the main display area, or you can specify the desired MGR code the
   first time.  Remember that no checking is done if you choose to override the
   default device manager.  In this case it is your responsibility to make sure
   the chosen device manager can really work with the chosen device.

   Parameters may be typed into the "FN/P" fields at any time.
   Just be sure to press ENTER to have them accepted.

   Usually no error checking is done by the Configurator on FN/P field
   parameters, except for AWSICE and AWSCHAN devices for which the "remap"
   checking option is activated. See their .DOC files for details.

2. ADD a DASD device to DEVMAP, and ALLOCATE the file at the same time:
   Move the cursor to the first entry field (the ">" underneath the "Addr"
   heading), type in the real address, volume label, allocation type, file
   size and OS/2 filename then press ENTER to allocate the file.  You must
   specify the device type if DMKRIO.ASM is not present.  For VSE volumes
   you must specify the allocation type of "VSE". For Count-Key-Data devices
   (e.g. 3380) don't specify any allocation type -- all CKD volumes MUST be
   initialized via ICKDSF; the configurator does not perform any initialization

 Note: All FBA allocation types except PERM and TDSK will be zeroed when the
       the OS/2 file is created. If you need either of these zeroed, then use
       the "/Z" option of the ALC.EXE OS/2 utility after creating just the
       DEVMAP entry as instructed in 3. (below).

   If you do not specify a OS/2 drive letter (d:) or an OS/2 subdirectory then
   the drive letter and subdirectory will be taken from the "Path >" field
   displayed at the top of the frame.  If a different drive is specified
   but no subdirectory, then the current subdirectory on that drive will be
   used.  You can also type in any valid OS/2 drive and subdirectory.

   If you do not type anything into the FN/P field, then a filename will be
   created for you of the form:  LABEL.ADR.  If this volume is a 3390 device
   of greater than 2519 cyls, then two files will be created: label_1.adr
   and label_2.adr.

   Note that although the file is allocated IMMEDIATELY, the device entry is
   not added to DEVMAP until you select "F6 END - SAVE ALL UPDATES" from the
   FUNCTIONS main menu when you exit the Configurator.  If you instead choose
   "F10 QUIT - DO NOT SAVE ANYTHING", the OS/2 file will still exist without a
   corresponding device entry.  If you do not want to keep the file, use the
   OS/2 ERASE command to delete it.  If you change your mind and want to use
   this file, reinvoke the Configurator and follow instruction 3., listed
   immediately below.

3. ADD a DASD device to DEVMAP, but WITHOUT allocating the OS/2 file:
   Move the cursor to the first entry field (the ">" underneath the "ADDR"
   heading) and type in the real address.  Move the cursor (with the TAB key)
   to the rightmost field (FN/P), type in the desired OS/2 filename and press
   ENTER.  A new DASD device record will be added to the main display area at
   the chosen real address, but no file will be allocated (Size field is
   blank).  If the file already exists then the Label, Atype, and Size fields
   will be filled in with the actual file's information.


MANIPULATING EXISTING DEVICES

You can allocate OS/2 files for predefined DASD device entries, delete or
temporarily exclude any type of device entry, or change filename search
information or P/390 session descriptions.

There are six modes of operation for existing devices:

1. ALLOCATE a OS/2 file for an existing device entry: (F11 key)
   If a DASD device entry has no Size information, this means that there is no
   real minidisk file on your PC disk.  Move the cursor under the line of the
   device you want to allocate and press F11.  The line will be REMOVED from
   the main display area and placed into the data entry line at the top.  You
   should complete or correct all required information and then press ENTER to
   allocate the file.  If the allocation is successful, the entry line will be
   moved back into the main display area. Otherwise you will be instructed via
   error messages how to proceed.

2. DELETE a DEVMAP device entry: (F9 key)
   Place the cursor UNDER the line of the one you want to delete and press F9.
   The line will be highlighted and you will be asked to confirm the deletion
   by pressing F9 again.  If there is a OS/2 file associated with this entry
   (the FILENAME field and SIZE fields are not blank) then you will be asked
   whether you want to also delete the OS/2 file that holds the minidisk.  If
   you press F9 again, the OS/2 file will be deleted IMMEDIATELY.  The device
   entry will not be deleted from DEVMAP until you select "F6 END - SAVE ALL
   UPDATES" from the FUNCTIONS main menu when you exit the Configurator.

3. EXCLUDE a range of devices: (ALT+F3 key)
   Place the cursor under the line of a device you want to exclude and press
   ALT+F3.  All device entries beginning with that address and continuing
   through that RANGE of addresses will be excluded.  They will now be
   displayed on the screen in dark blue (underscored on monochrome displays)
   and the device manager code will be changed to 0.

   If you want to exclude ALL devices which are handled by a particular
   manager, move the cursor under the appropriate name in the "Mgr Codes"
   list (which is located below the main display area) and press ALT+F3.
   All devices addresses which are assigned to that manager code will
   simultaneously be excluded and the manager name will also be displayed
   in dark blue (underscored on monochrome displays).

4. RESTORE excluded devices: (ALT+F5 key)
   Place the cursor under the line of a device you want to restore and press
   ALT+F5.  All device entries beginning with that address and continuing
   through that RANGE of addresses will be restored.  They will be displayed
   on the screen in their normal color or intensity and the device manager
   code will be restored to its original value.

   If you want to restore all devices which are handled by a particular manager
   move the cursor under the appropriate name in the "Mgr Codes" list (which is
   located below the main display area) and press ALT+F5.  All device addresses
   which are assigned to that manager code will simultaneously be restored and
   the manager name will be redisplayed in its normal color (yellow).

5. CHANGE OS/2 filenames or P/390 session descriptions:
   In the main display area you can only change the rightmost field on each
   line which contains:
       - OS/2 filename (for DASD, emulated tapes, or printers).
       - P/390 Session Titles (for displays).
       - 3088 Remote Names (for LAN3088 connections).
       - parameters or (or comments) for all other device managers.
   To change this data, move the cursor to the entry field (using the TAB or
   arrow keys), type over the existing data, and then press ENTER.

   Note that changing the filename field of DASD entries does NOT rename the
   OS/2 file.  It only allows you to change the OS/2 disk, subdirectory and
   filename which are used to locate the minidisk volume.  In order to rename
   or move the OS/2 file you must use regular OS/2 commands BEFORE entering the
   Configurator.

   A special case occurs for DASD if the first character of the OS/2 filename
   is an asterisk (*).  This provides a method of temporarily excluding a
   single DASD device (as opposed to a range of devices with ALT+F3, described
   above).  To restore the device, simply delete the asterisk and press ENTER.

6. CHANGE a Volume Label:
   Place the cursor under any part of the volume name field and press ALT+F2.
   This field will become unprotected and red in color. Type in a new volume
   name and press ENTER. If any errors occur, follow the instructions in the
   error message. If the file exists, BOTH the DEVMAP entry and the volume
   name found in the OS/2 file (VM or VSE volume) will be changed. If the file
   does not exist, only the DEVMAP entry will be changed. If an error occurs
   while trying to write the new volume name into the file, the new DEVMAP
   entry is cancelled and reverts back to the original name.
<>
/*----------------------------------------------------------------------*/
/* the Device Manager Parameters submenu help                           */
/*----------------------------------------------------------------------*/
cndevprm
This screen displays the parameters that are passed to each P/390 device
manager when it is started from IPL.CMD.

A maximum of 54 characters may be specified for each manager. The format
of the parameters is manager dependent and is described in the *.DOC
files for each manager. To view a particular manager's DOC file, move
the cursor onto the manager's line and press F1.

The defaults are taken from the file AWSCPARM.MGR. If a manager has
no parameters then the field will be blank.

If you want to revert back to the default parameters for any manager,
blank out the line and press ENTER.

If a manager has default parameters, but you want to pass NO parameters,
type in the word "none" (without the quotes). This will cause IPL.CMD to
pass blanks to the device manager.

After modifying any of the manager parameters, press ENTER to make them
accepted. They are saved in the DEVMAP file when you "END - Save and Exit"
from the Configurator main menu.

You can have different device manager parameters in different DEVMAPs,
e.g. for multiple operating systems or different I/O configurations.
<>
/*----------------------------------------------------------------------------*/
/* end of the help messages.  DO NOT ERASE THESE LINES                        */
/*----------------------------------------------------------------------------*/
