HP 3000 Manuals HP 3000 Manuals
RUNNING ENTRY
In order to display the forms for data entry, you run ENTRY. To do this,
first turn on your terminal and then press RETURN. A colon prompt (:) is
displayed on the screen. You log on in response to this prompt. Logging
on means that you request access to the MPE operating system that
controls all HP 3000 system operations. (Refer to Using the HP 3000 or
HP 3000: A Guided Tour for an introduction to using the HP 3000 Computer
System.)
In order to log on, you must know your user name and account name (and
possibly other information such as passwords or a group name). Ask your
system manager for this information, and then log on with the :HELLO
command as follows:
:HELLO username.accountname
The words in capital letters must be entered exactly as shown; the
lowercase words are replaced by the specific names or numbers supplied by
your system manager. Only the username and accountname are shown here;
if passwords and groupname are also needed, the system manager can
explain how to enter them. Suppose your user name is JOAN and your
account name is INVENTRY, you log on with the following command:
:HELLO JOAN.INVENTRY
Then press RETURN to enter your log on command into the operating system.
When the system accepts the log on, it returns a "welcome" message
followed by another colon prompt (:). In response to this second prompt,
type the following command to run ENTRY:
:RUN ENTRY.PUB.SYS
Then press RETURN.
Specifying ENTRY Files
Once ENTRY is in control, it must know the name of the forms file in
which the data entry forms are stored. It must also know the name of the
"batch" file in which the data you enter is to be saved. If you do not
know the names of these files, ask your system manager.
Forms File. The forms file is a standard MPE file identified by its data
file name. It may be fully qualified by account and group name and
lockword.
Batch File. The batch file is a standard MPE file. If the named batch
file does not exist, a new file is created automatically. If the file
already exists, it is opened so that new data can be added to the end of
the existing data in the file.
ENTRY prompts for the forms file name as follows:
ENTER FORMS FILE NAME AND PRESS RETURN:
In response to this prompt, type the forms file name you want and then
press RETURN. If a password is associated with a forms file, ENTRY will
prompt the user for it twice. This is because the VPLUS/V intrinsic must
open the formsfile twice, once to determine the forms file type (KSAM or
non-KSAM) and again to open it in the correct mode. If you wish to avoid
being prompted twice for the forms file password, enter it along with the
forms file name in the format: formsfile/lockword. ENTRY then prompts
for the batch file name:
ENTER BATCH FILE NAME AND PRESS RETURN:
Enter the batch file name. If the batch file name you entered is an
existing file to which data has already been written, you may receive the
following message:
WARNING: Forms file recompiled since this
batch was created. Enter "Y" to continue:
This message is issued if the forms file has been modified and recompiled
since it was last used to collect data to the batch file. Enter Y to
continue only if you are sure that the changes to the forms file will not
invalidate data already entered on the file. Otherwise, press RETURN.
This causes the forms file prompt to be re-issued so you can enter a
different forms file name and/or a new batch file name. Generally, you
should use a new batch file when a forms file is recompiled.
If the batch file you named was originally used with a different forms
file than the one you named, you will receive this message:
WARNING: A different forms file was used to
create this batch. Enter "Y" to continue:
This message may mean that the wrong forms file was entered. If you
press RETURN, the forms file prompt is issued again so you can enter the
correct forms file name. If the forms file name was correct, but the
batch file name is wrong, you must reenter the forms file name and then
enter a different or new batch file name when the batch file prompt is
issued. Normally, in this situation, you will not enter Y to continue
since it makes no sense to use a batch file that does not match the forms
file.
If the forms file has been designed to accept data using a native
language other than NATIVE-3000 and ENTRY does not know the exact
language which should be used you may receive the message:
ENTER LANGUAGE ID NUMBER AND PRESS RETURN:
If you receive this message and do not know the appropriate number,
contact your system manager. For more information on Native Language
Support, see Section 8.
Removing Deleted Records From a Batch. When records are deleted from a
batch file, they are only "tagged" for deletion. If you wish to
physically remove deleted batch records, you use the HP file copier,
FCOPY. The following FCOPY operation will work:
1. Determine the record size of the batch file (in bytes) by using
the MPE :LISTF command. Let this value be N.
2. The delete flag is located 19 bytes from the end of a batch
record, or at location N-19. Let this value (N-19) be M.
3.
:RUN FCOPY.PUB.SYS
>FROM=oldbatch;TO=newbatch;SUBSET=#0,0#,M;NEW
>EXIT
4. If desired,
:PURGE oldbatch
:RENAME newbatch,oldbatch
Expanding the Batch File. In most cases the batch file built for you by
ENTRY has enough space, but if you wish to enter a large amount of data
(large enough to fill over 1023 copies of a form, or 1023 records), you
must either build a larger batch file before running ENTRY, or increase
the size of your existing batch file. To build a larger batch file,
first use the MPE :FILE command before running ENTRY:
:FILE filename;DISC=numrec
where filename is the name of the batch file and numrec is the number of
records you want the new batch file to have. When you run ENTRY, specify
*filename as your batch file, and the program will build it to have the
number of records you requested.
You can also use FCOPY to enlarge an existing batch file. Once again,
first issue the MPE :FILE command:
:FILE filename;DISC=numrec
Then run FCOPY to build a new, larger file of the size you requested and
copy the existing data into it:
:RUN FCOPY.PUB.SYS
When you see the FCOPY prompt, a "greater than" sign, type:
>FROM=oldname;TO=*filename;NEW
where oldname is the name of your existing batch file and filename is the
name of your new, larger file. Remember to include the asterisk;
otherwise the new file will be no larger than the old one. After the
"greater than" sign reappears, type EXIT and press RETURN.
The last step is to purge the old batch file from the system and give its
name to your new batch file:
:PURGE oldname
:RENAME filename,oldname
where oldname and filename are the names of your old and new files,
respectively. When you next run ENTRY, specify oldname as the batch
file, and you may continue entering data as before.
Block Mode
After the ENTRY files have been specified, ENTRY operates in "block
mode". During log on, when you request ENTRY, and when you specify the
forms and batch file names, your commands are entered into the system by
pressing RETURN at the end of each line. When ENTRY operates in block
mode, your data is entered only by pressing ENTER. This allows you to
move around on the screen, pressing RETURN if you wish, and to type in or
correct data. ENTRY does not receive any keyed data until ENTER is
pressed.
Once the forms and batch files have been specified, ENTRY starts
displaying the forms defined in the specified forms file. The data you
enter in each form displayed on the screen is stored in separate records
of the specified batch file. Subsequently, you can look at or modify the
data stored in the batch file as described below under "Data
Modification".
Local Form Storage
Some terminals have a feature that allows forms to be stored locally in
terminal memory. Forms stored in the terminal can be displayed on the
screen directly rather than having to be retrieved from the memory area
of the computer. This feature, with look ahead mode, is automatically
activated when you run ENTRY. Refer to Appendix G for a list of supported
terminals; refer to Section 6 for more information on Local Form Storage.