HP 3000 MPE/iX Computer Systems Using HP 3000 MPE/iX: Advanced Skills Tutorial ABCDE HP Part No. 32650-90872 Printed in U.S.A.
The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability or tness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for direct, indirect, special, incidental or consequential damages in connection with the furnishing or use of this material.
This is the rst edition of Using HP 3000 MPE/iX: Advanced Skills Tutorial. It is a replacement for the Using the 900 Series HP3000:Advanced Skills which was printed in separate modules. This is intended for MPE/iX users who have completed Using HP 3000 MPE/iX: Fundamental Skills Tutorial, hereafter referred to as Fundamental Skills. This self-paced course has hands-on exercises now contained in one booklet. There are six study modules composed of a number of lessons.
Contents 1. Begin Here Materials List . . . . . . . . Course Overview . . . . . . Course Description . . . . Course Goal and Objectives Orientation . . . . . . . . Reference Documents . . . Conventions . . . . . . . Course Instructions . . . . . Setup Instructions . . . . . Equipment . . . . . . . . Procedure Summary . . . Step-by-Step Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the MKACCT Command File to Create Accounts, Groups, and Users . . . . . . . . . . . . . . . . To create an account, groups and users . . . . . . Using MKACCT to add groups or users to an existing account. . . . . . . . . . . . . . . . . . . . Making changes later . . . . . . . . . . . . . . . Problems with MKACCT . . . . . . . . . . . . . Capability Requirements for Applications and Programs Lesson Summary . . . . . . . . . . . . . . . . . . Exercise 1-4: Lesson 2 Review . . . . . . . . . .
Lesson 3 Creating Temporary Files . . . . . . . . Introduction . . . . . . . . . . . . . . . . . $NEWPASS and $OLDPASS . . . . . . . . . . Exercise 2-3: $OLDPASS . . . . . . . . . . $NULL . . . . . . . . . . . . . . . . . . . . Lesson summary . . . . . . . . . . . . . . . Lesson 4 Using File Equations . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . Writing le equations . . . . . . . . . . . . . Bene ts of the FILE command . . . . . . . . Backreferencing . . . . . . . . . . . . . . .
Suspending a job . . . . . . . . . . . . . . Altering a job . . . . . . . . . . . . . . . Lesson summary . . . . . . . . . . . . . . Lesson 4 Monitoring Jobs . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . SPOOLER commands . . . . . . . . . . . . Displaying spool le information . . . . . . . Input and output spool les . . . . . . . . . Where spool les are kept . . . . . . . . . . Using PRINT to check for errors . . . . . . . Aborting jobs . . . . . . . . . . . . . . . .
Exercise 5-1: lesson 1 review . . . . . . . . . . . Lesson 2 Understanding Search Priority and Search Path Introduction . . . . . . . . . . . . . . . . . . . . UDC directory . . . . . . . . . . . . . . . . . . . Command directory . . . . . . . . . . . . . . . . . File directory . . . . . . . . . . . . . . . . . . . . Search path . . . . . . . . . . . . . . . . . . . . XEQ command . . . . . . . . . . . . . . . . . . . Lesson summary . . . . . . . . . . . . . . . . . . Exercise 5-2: lesson 2 review . . . . .
7. Module 6: Variables and Expressions Challenge Test . . . . . . . . . . . . . . Lesson 1 Understanding Variables . . . . . Introduction . . . . . . . . . . . . . . Command les in this lesson . . . . . . . STATS command le: . . . . . . . . . LF command le: . . . . . . . . . . . Assigning and displaying variable values . Variable names . . . . . . . . . . . . . Variable types . . . . . . . . . . . . . System-de ned variables . . . . . . . . User-de ned variables . . . . . . . . . Deleting variables . . . .
Exercise 3-1: Lesson 1 Review . . . . . . . . . Lesson 2 Examining a Job File . . . . . . . . . . . Exercise 3-2: Lesson 2 Review . . . . . . . . . Lesson 3 Creating and Streaming a Job File . . . . Lesson 4 Monitoring Job Progress . . . . . . . . . Exercise 3-4 Aborting a Job and Using PRINT . . Solutions to Module 4: File Transfer . . . . . . . . . Check Your Answers . . . . . . . . . . . . . . . Lesson 1 Using FCOPY . . . . . . . . . . . . . . Exercise 4-2 Appending One File to Another . . .
Figures 2-1. 2-2. 2-3. 2-4. 2-5. 3-1. 3-2. 3-3. 3-4. 3-5. 3-6. 3-7. 3-8. 3-9. 4-1. 4-2. 4-3. 4-4. 4-5. 4-6. 4-7. 4-8. 5-1. 5-2. 6-1. 6-2. 6-3. 6-4. 6-5. 6-6. 6-7. 6-8. 6-9. 6-10. 6-11. 6-12. 6-13. 7-1. 7-2. 7-3. Contents-8 Account Manager . . . . . . . . . . . . . . . . . Managing Groups . . . . . . . . . . . . . . . . . Sample Worksheet . . . . . . . . . . . . . . . . LISTUSER Command . . . . . . . . . . . . . . . User Capabilities in One Account . . . . . . . . . File Types . . . . . . . . . . . . . . .
Tables 2-1. ACD Permissions . . . . . . . . . . . . . . . . . .
1 Begin Here The following instructions present the information you need to get started with Advanced Skills. Materials List The Student Kit consists of all parts listed below: Begin Here Module 1: Account Management Module 2: File Management Module 3: Batch Processing Module 4: File Transfer and Storage Module 5: User Commands Module 6: Variables and Expressions Solutions Guide Glossary of Terms MPE/iX Lab Tape Note Your introduction to this course with instructions for setting up training session.
\Setup Instructions" section of \Begin Here" for speci c instruction on how to install the lab tape and set up student accounts. Each lesson of each module contains questions and exercises. Solutions are found in the Solutions Guide. As you do the exercises, keep the Solutions Guide handy so that you can follow along and check your responses.
Reference Documents The following manual is used with the course: MPE/iX Commands Reference Manual You may use the online Help Facility while studying any of the modules in this course. Enter HELP4Return5 at the system prompt to start the Help Facility. When you want to leave the Help Facility, enter: EXIT4Return5. Conventions Read this important information before you begin to do the modules. These modules use instructions and di erent typefaces to clarify what to read and what to do.
Course Instructions 1. When performing the exercises in this course, you must log on as follows: HELLO USERx.ACCTx Account password = APASSx User password = UPASSx X Means In each of these passwords, the x is a two-digit user identi er that should be provided by the person responsible for setting up accounts. That person may also have assigned you di erent account and user passwords due to system security. Find out what your user identi er is before you begin any of the hands-on activities.
Setup Instructions Note The person responsible for setting up your accounts for this course, must have system manager (SM) capability to install the course material. Ask your system manager to install the material according to the following instructions. This section helps you create the account structure for all users doing the MPE/iX exercises associated with this training.
Note Execute MOVEFILE only if you are setting up Advanced Skills accounts. This le creates job les that let you log on to each student account and move les over from the instructor account. 6. Execute the CLEANUP command le to perform le management activities. 7. Remove the tape from the tape drive and store it in a safe place. 8. Create new student accounts as needed. 9. Purge existing student accounts as needed. Each of the steps will now be explained. Step-by-Step Procedure 1.
e. You should now have ACCT0, the instructor's account, on disk. Enter the following command to verify that there are 42 les in the account: LISTFILE @.@.
Note The instructor account or manager of the course, using USER0 and ACCT0, now has extended capabilities beyond those of the student, in order to be able to monitor or amend student accounts as needed. You may wish to replace MORE and MONEY with meaningful passwords of your choice. Use the ALTACCT and ALTUSER commands to do so. 3. Log on as the instructor and activate UDCs: a. Log on as USER0.ACCT0: HELLO USER0.ACCT0 (home group = CLASS) Account password: MORE User password: MONEY b.
Note Q lets you QUIT, P lets you PURGE the accounts. Use P to purge individual or all accounts in either course whenever necessary. What is the number of the first account/user you wish to create or purge? Respond with 1 when you are rst setting up the accounts. See step 7 if you are adding more accounts. What is the number of the final account/user you wish to create or purge? Respond with a number representing the last account you wish created - usually the same as the total number of students.
What is the number of the final account you wish to create or purge? Respond with a number representing the last account you wish purged|usually the same as the total number of students. You now see this message: *** ACCTx through ACCTy will be purged *** Proceed with purging? (Y/N) Respond Y if you wish to continue purging the old accounts.
*** Creating account ACCT1 for Fundamental Skills *** *** Creating account ACCT2 for Fundamental Skills *** . . . *** Creating account ACCT10 for Fundamental Skills *** *** 10 accounts created *** Example #2: Suppose those users now wish to take the Advanced Skills course.
Example #3: Suppose you purged or never had the Fundamental Skills course student accounts and you now wish to create ten Advanced Skills course student accounts. Your responses to the prompts would be as follows: Are you setting up the Fundamental Skills course? N Are you setting up the Advanced Skills course? Y ************************************************************ *** ACCTx accounts may already exist for the Fund. Skills *** *** course.
account and execute the COPYFILE command le. COPYFILE does the actual copying of les from instructor to student account. a. Issue the following command: MOVEFILE b. Answer the prompts as you did when executing ADVSETUP: *** ENTER A ZERO (0) TO TERMINATE WHEN ANSWERING PROMPTS *** What is the number of the first student account you just added? What is the number of the final student account you just added? c. As MOVEFILE executes for each student account, you see several messages on the screen.
MYUDC1 MYUDC2 MYUDC3 PR PRX RECUR SJT STATS TERTIME e. The account users are USER1 to USERx. The home group is CLASS, and the logon is: HELLO USERx.ACCTx Account password: APASSx User password: UPASSx 6. All student accounts now contain their necessary les. At this point, perform le management activities to resecure les, delete variables, and purge temporary les created during MOVEFILE and COPYFILE execution.
TOTAL: 3136 sectors b. Advanced Skills Course: You need the following amount of disk space for the initial student and instructor accounts GROUP and ACCOUNT DISK SPACE BY SECTORS Course Manager or Instructor: CLASS.ACCT0 PUB.ACCT0 PROJECT.ACCT0 MYGROUP YOURGRP 2128 16 0 64 0 SUBTOTAL: 2208 sectors CLASS.ACCT PUB.ACCTx PROJECT.ACCTx 1552 16 0 SUBTOTAL: 1568 sectors Student: TOTAL: 3776 sectors 8. Create additional student account(s) as needed: a. Use ADVSETUP to create the accounts.
************************************************************* *** ACCTx accounts may already exist for the Fund. Skills *** *** course. Be careful not to purge any accounts *** *** that may still be in use. If any accounts on the *** *** system are no longer in use, you can purge them and *** *** reuse them for the Adv. Skills course by answering *** *** YES to the following prompt. *** ************************************************************* Do accounts/users from Fund.
*** system are no longer in use, you can purge them and *** *** reuse them for the Adv. Skills course by answering *** *** YES to the following prompt. *** ************************************************************* Do accounts/users from Fund. Skills already exist (Y or N): Y *** Press P to purge old Fund. Skills accounts.
2 Module 1: Account Management Module 1 presents the following basic and advanced account management concepts: Lesson 1 Managing Your Account Lesson 2 Managing Account Groups Lesson 3 Managing Users Challenge Test 1. De ne the following account capabilities and note the ones that are default. AM AL GL ND SF BA IA PH 2. Indicate who (account manager, general user, or system personnel) can do the following: a. list information on their account b. change their account capabilities c.
Lesson 1 Managing Your Account Lesson 1 Managing Your Account Figure 2-1. Account Manager Introduction 2-2 Module 1: Account Management Lesson 1 presents the following information about managing your account: listing account information meaning of access codes passwords|usage and security In this and the following lessons, you learn more about account management, and how to become more e ective in your interaction with the MPE/iX system.
Lesson 1 Managing Your Account Note Listing Account Information When you complete this course, you may want to check with your system manager about getting an account with AM capability, if warranted, for your processing requirements. If you haven't already done so, please log on to the account speci ed by your system manager or supervisor.
Lesson 1 Managing Your Account After you review this information, list the de nitions of the account capabilities below: Q1-1 Account Capabilities: AM = AL = GL = *ND = *SF = *BA= *IA = PH = Note Note The capabilities noted with the asterisk in Q1-1 are default capabilities. The default capability set, ND, SF, BA, and IA, is required in order to process, store, and print information from an MPE/iX system and peripheral devices such as printers, magnetic tape, and disk drives.
Lesson 1 Managing Your Account ANY = Any user (on the system) AC = Member of this account only GU = Member of this group only AL = Account librarian only GL = Group librarian only CR = Creating user only Check the NEWACCT command information for an explanation of the user code AC. Q1-3 Use of your account has been restricted to which user(s)? Logon Password Files belonging to the users of an account should be protected from unauthorized personnel trying to log on to that account.
Lesson 1 Managing Your Account Q1-4 Lesson Summary Which practices identify good account security? a. changing passwords regularly b. not using well-known names, such as a nickname, for passwords c. protecting passwords from unauthorized users d. not entering passwords in your logon e. all of the above 1. Use the LISTACCT command to list information on your account. 2. Only system management may set and change session and job limits as well as account capabilities and account passwords. 3.
Lesson 2 Managing Account Groups Lesson 2 Managing Account Groups Introduction Lesson 2 presents information on: listing account groups de ning capability and access attributes adding, modifying, and deleting account groups verifying program capabilities with VERSION To help you keep track of the les in your account, MPE/iX allows account managers to create individual groups with speci ed attributes and capabilities.
Lesson 2 Managing Account Groups Group Assignments (account manager) With several users using one account, many account managers choose to assign individual users to speci c groups. They also use the PUB group for les of interest to all users. If you are the only user of your account, you may want to consider setting up individual groups for di erent projects or purposes. No limit exists on the number of groups that you may have in a single account.
Lesson 2 Managing Account Groups Note For general users the LISTGROUP command displays only information for their current group. Q1-6 A user having account manager capability is able to list information for which groups? Users without account manager capability may only list information for which groups? Group Attributes Each group is assigned certain attributes selected by the account manager or by the system (default). These attributes can be assigned when the group is created or modi ed.
Lesson 2 Managing Account Groups Group File Access Attributes File access attributes specify the mode of access that a type of user can have. When a group is created, each type of le access is noted with a single letter abbreviation as follows: R = Read L = Lock A = Append W = Write (implies A and L) X = Execute S = Save As you remember from the rst lesson, user types are also identi ed with an abbreviation.
Lesson 2 Managing Account Groups Access Control De nitions Access codes provide one level of security. They provide security for accounts and groups. Another level of security works on individual les. It allows you to protect speci c les (or collections of les). This second level of security is called access control de nitions (ACD). ACDs are provided to meet the requirements of National Computer Security Center.
Lesson 2 Managing Account Groups Table 2-1. ACD Permissions Meaning Permission R Read W Write A Append L Lock X Execute NONE None RACD Read/Copy The user who has this permission can look at or copy the le. The user who has this permission can add information anywhere in the le. This implies the ability to change existing information. The user who has this permission can add information to the le, but only at the very end of the le.
Lesson 2 Managing Account Groups do not have any access to the le. (Account managers and system managers automatically have access to les: account managers \own" all of the les in their account(s); system managers \own" all of the les on their system.) Notice that the two parts are separated by a colon ( : ). You can make several ACD assignments at once, as in this example: ALTSEC TAXRETRN;NEWACD=(R,W:JOHN.BUDGET;R:MARIA.BUDGET; & NONE:MARK.BUDGET,@.
Lesson 2 Managing Account Groups Adding a New Group (account manager) If you have account manager (AM) capability or higher, you may add a new group to your account. The command that you use to do this is: NEWGROUP Exercise 1-2: Using NEWGROUP (account manager) The purpose of this exercise is to illustrate how to create account groups with default attributes as well as those with attributes that you specify. The NEWGROUP command with its parameters is listed below.
Lesson 2 Managing Account Groups ********** End of Exercise 1-2 ********** Altering Group Attributes (account manager) The ALTGROUP command is used to change group attributes; however, like the NEWGROUP command, the ALTGROUP command also requires account manager level capability or higher for its use. ALTGROUP groupname;attribute= The ALTGROUP command can be used to change any attributes, provided that these attributes do not exceed the limits for your account.
Lesson 2 Managing Account Groups Use the PURGEGROUP command to delete the STOP and SLOW groups. Using the MKACCT Command File to Create Accounts, Groups, and Users There is an alternative to using MPE/iX commands to create the accounts, groups, and users on your system. The command le MKACCT (MKACCT.MPEXL.SYS) provides you with an easy, interactive method of creating your account structure.
Lesson 2 Managing Account Groups 1. Log on as MANAGER.SYS. 2. Type MKACCT.MPEXL at the system prompt, and press 4Return5. :MKACCT 4Return5 The following MKACCT information appears on your screen: ************************************************************************ * MKACCT allows you to create: ACCOUNTS, GROUPS, and USERS. * * * * ACCOUNTS contain GROUPS and USERS. GROUPS contain your files. * * The next screen shows a picture of an account structure.
Lesson 2 Managing Account Groups If you type NO, MKACCT will ask you if you want to add groups or users to an existing account. For more information on this topic, see the following task, \Using MKACCT to add groups or users to accounts." If you type EXIT, MKACCT will stop and ask you to con rm your intention of stopping MKACCT. If you type YES, MKACCT will start the process for creating an account. 4. When you are ready to create an account, type YES, or press 4Return5, at this prompt.
Lesson 2 Managing Account Groups Answer YES when the \Create this group (Yes,No,Exit)?" prompt appears to nalize the creation of the group. MKACCT will continue to prompt you for new group names until you type NO at the \Do you want to create a new group . . . ?" prompt. You do not need to create a PUB group. MKACCT does this automatically. 7. MKACCT then asks, \Do you want to create a new user in the ACCTNAME account (Yes,No,Exit)?". To create a new user, type YES, or press 4Return5, at this prompt.
Lesson 2 Managing Account Groups 9. After carefully reading this screen, press 4Return5 to view the next screen. *************************************************************** * * * * * To create more GROUPS, USERS or ACCOUNTS just execute * * MKACCT again.
Lesson 2 Managing Account Groups 7. When prompted supply a new user name and password. MKACCT will continue to prompt you for new user names until you type NO or EXIT at the \Do you want to create a new user in the ACCTNAME?" prompt. 8. When you have nished adding new groups and users to your existing account, type EXIT at any prompt that ends with the (Yes,No,Exit)? options.
Lesson 2 Managing Account Groups Lesson Summary 1. A minimum of account manager capability is required to do the following: a. Display information about all groups in your account. b. Create, modify, and delete account groups. c. List all passwords in your account. 2. The MKACCT command le allows a system manager to create accounts, groups, and users on the system in a question-answer format. 3. The REPORT and LISTGROUP commands provide information on groups within an account. 4.
Lesson 3 Managing Users Lesson 3 Managing Users Introduction Lesson 3 presents the commands associated with the following user-related tasks: displaying user information creating new users Altering characteristics of existing users You have logged on to the system and started an interactive session. Previously, you used SHOWJOB to look at some of the users on the system. You will now learn more commands to help you manage and monitor those users.
Lesson 3 Managing Users parameter names are displayed in lowercase letters. If the parameters are required (no brackets), you must replace them by actual values. Optional parameters are shown surrounded by brackets [ ]. You do not have to specify values for such parameters. If you do not specify an optional parameter in a command line, a default value(s) is assigned. When the syntax shows that a comma is associated with an optional parameter, you must omit that comma, too, when you omit the parameter.
Lesson 3 Managing Users Here is a simple example of command syntax: LISTUSER [userset][,listfile][;PASS] Here is an example of the corresponding command: LISTUSER @.MYACCT userset Is all of the users (@) in the MYACCT account. listfile Defaults to the terminal (you see the listing there). Note that the comma (,) associated with listfile is omitted because listfile is omitted. Is not speci ed, so no passwords are displayed.
Lesson 3 Managing Users Hint: After executing the command, use the PRINT command to print the contents of INFO. 5. Try to list all of the users on the system. You get this message: EXECUTING THIS COMMAND ON ALL ACCOUNTS REQUIRES SYSTEM MANAGER CAPABILITY (CIERR 724) You cannot look at all of the users because you do not have system manager capability. You will learn about system manager capability and other capabilities later in this lesson. 6.
Lesson 3 Managing Users Q1-13 Suppose that there is a user called MYUSER in your account, and you wish to change that user's password to MYPASS. Which command would you use? a. How would this a ect MYUSER during the current session? After MYUSER logs o and logs on again? b. What capabilities must you have to change a user password for a user in your account? To change a user password for a di erent user in a di erent account? Now change your own password to MYPASSX (X=user number).
Lesson 3 Managing Users You now have an account with three users, each of whom has slightly di erent capabilities: USERx: AM,IA,BA,SF,ND,PH USERxA: IA,BA,SF,ND USERxB: IA,BA,SF,ND,PH Figure 2-5. User Capabilities in One Account As long as the users' capabilities do not exceed the account capability, an account may have multiple users who have di erent capabilities. This provides a way to implement a security scheme that controls the capabilities of individual users within the same account.
Lesson Summary 1. The online help facility displays information on speci c MPE/iX commands which are also described in the MPE/iX Commands Reference Manual Volumes 1 and 2 (32650-90003 and 32650-90364). . 2. The basic syntax conventions for MPE/iX commands are Keywords are displayed in UPPERCASE letters. Parameters are displayed in lowercase letters. Optional parameters are displayed in lowercase letters, enclosed in square brackets [ ].
3 Module 2: File Management Module 2 presents the following lessons on creating and using les and le equations: Lesson 1 Introducing Files Lesson 2 Building Disk Files Lesson 3 Creating System-De ned Temporary Files Lesson 4 Using File Equations Challenge Test 1. Which commands provide the following le information? a. record and (sector) space information b. creator and modi cation information c. hex le information d. logical record size information e. fully quali ed le names by group 2.
6. Write a le equation that designates le PRT as the line printer (LP). Then use the PRINT command to print the contents of MYFILE1 on the line printer. (The command must reference le PRT). Note 3-2 Module 2: File Management Lesson 3 is required for programmers and anyone taking Using the 900 Series HP-3000: Programmer Skills.
Lesson 1 Introducing Files Lesson 1 Introducing Files Introduction Lesson 1 presents the following information: LISTFILE parameters to display le information an introduction to permanent les an introduction to temporary les (user-de ned and system-de ned) An introduction to formal le designators Figure 3-1. File Types The MPE/iX le system controls the processing of all les, including their storage and transfer between various devices.
Lesson 1 Introducing Files Permanent les LISTFILE command options Permanent les are sometimes referred to as \user les" since they are created directly by you, the user. You are probably already familiar with the le naming requirements, saving and purging commands, and basic LISTFILE commands to list your permanent les; however, as you continue to create and use more permanent les in MPE/iX, you need to know more about this kind of le, its characteristics, and how to get information about permanent les.
Lesson 1 Introducing Files Can you get logical record information for the le, JOB1? Try that now. Which record size is larger, JOB1 or MYFILE1? (Compare the sizes.) Record size information is helpful when you want to join les together or use a word processing application to make changes to a le. If the application cannot accept the le, you see the message: CANNOT EDIT FILES OF THIS TYPE Note You can enter LISTFILE filename,SUMMARY to get the same display provided by LISTFILE filename,1.
Lesson 1 Introducing Files Q2-1 Match the LISTFILE commands with the information that they display. LISTFILE,1 File structure, creation, and modi cation information LISTFILE,2 Logical record information LISTFILE,3 File space information LISTFILE,4 The purpose of the LISTFILE,4 option is to provide you with complete access information by account, group, and le, for each le in your current group. By entering LISTFILE,4 you see a display of information for all les in your current group.
Lesson 1 Introducing Files LISTFILE,7 The LISTFILE,7 command option displays le information exactly the way that LISTFILE,6 does, But if any of the les speci ed are KSAM or spool les, LISTFILE,7 displays information speci c to those specialized les. Since no KSAM or spool les have been created in this lesson, LISTFILE,7 duplicates the LISTFILE,6 information. Note You can enter LISTFILE filename,UNIQUE and get the same display provided by LISTFILE filename,7.
Lesson 1 Introducing Files When you log on, your system automatically de nes a le called $STDIN that corresponds to your input device, which is your keyboard. It also de nes a le called $STDLIST to which the system sends output. $STDLIST refers to your terminal screen. System les are also automatically created during compiling and linking. These temporary les are used by the system to hold data generated during processing.
Lesson 1 Introducing Files Listing temporary les How do you list temporary les? Use LISTFILE;TEMP. Enter that now and see if there are any temporary les in your account. LISTFILE;TEMP Unless you have been doing some programming or creating additional temporary les, you should only see the FILELIST that you just created. TEMPORARY FILES FOR USERx.ACCTx,CLASS FILELIST.CLASS.
Lesson 1 Introducing Files Q2-4 Lesson summary What is similar about the le naming characteristics of formal and permanent les? 1.
Lesson 1 Introducing Files 2. From each pair of commands, select the correct LISTFILE command that displays the information requested. a. b. c. d. e. f. g. h. i. Logical record and space allocation for all les in account. Hex information for MYJOB1 (requires AM capability). Logical record information for MYJOB1 le. Creator information for all les in your current group (requires AM capability). All les within your logon group.
Lesson 1 Introducing Files Lesson 2 Building Disk Files Introduction You have had a brief introduction to di erent types of les: permanent, temporary, and formal. In lesson 2, you will learn how to use the BUILD command and the following options to create customized les: record size blocking factor record type le type The BUILD command is useful when you need to change the le's format so that another program or subsystem can accept the format.
Lesson 1 Introducing Files Figure 3-2. BUILD Command Generally speaking, as a general user, you are not so much concerned with the characteristics of a le, as with the data in it. Usually, the subsystem that you are using (for example, some editor) automatically creates les with the appropriate characteristics that determine how the contents are stored on disk.
Lesson 1 Introducing Files Parameter filename lockword recsize blockfactor rectype filetype options Description MPE/iX le name Special password to restrict access to speci c le Record size (negative number is bytes, positive number is words) Ratio indicating number of logical records per physical block (R/B on the LISTFILE columns) Record type (F= xed-length, V=variable length, U=unde ned) Type of data (ASCII,binary) Device, le code, carriage control, and more Consider a le that already exists.
Lesson 1 Introducing Files MY/FILE You may think you have a le called MYFILE; however, the system interprets a le called MY with a lockword of FILE. Record size Record size refers to the number of bytes or words per record. Record size is important because certain applications can read only records of a certain size. You may nd that if a le has records of a di erent size, you will not be able to display or edit that le. This record size may vary according to the utility or program that created the le.
Lesson 1 Introducing Files Figure 3-3. Record Type Q2-7 File data type Other BUILD options What is the record type of MYFILE? Text les that you can view and edit tend to be ASCII. Executable program les and graphics les tend to be binary. In the next lesson you will have an opportunity to create some binary les.
Lesson 1 Introducing Files Exercise 2-2: creating a le to speci cation 1. Write the correct BUILD command to create to speci cation each of the les listed below. Whenever default values are speci ed, let the parameter default in the BUILD syntax. Note A list of codes appears in the help facility (at the system prompt, enter: HELP FILE FILECODE). The same information is available in appendix F of the MPE/iX Commands Reference Manual Volumes 1 and 2 (32650-90003 and 32650-90364). a.
Lesson 1 Introducing Files Lesson 3 Creating Temporary Files 3-18 Note System programmers must read this lesson. If you do not plan to do any programming, you may skip this lesson.
Lesson 1 Introducing Files Figure 3-4. Temporary Files When you compile and link a program, the following happens, as shown in gure 2-4: 1. Source code serves as input to the compiler. 2. The compiler builds $NEWPASS and writes compiled code to $NEWPASS. 3. When compiling is done, $NEWPASS is closed and renamed $OLDPASS (automatically). $OLDPASS contains the object code. 4. The linker uses $OLDPASS as input. 5. The linker builds $NEWPASS and writes linked, executable code to $NEWPASS. 6.
Lesson 1 Introducing Files Exercise 2-3: $OLDPASS Follow the designated steps to generate $OLDPASS. 1. Make sure that you are logged on as USERx.ACCTx in the CLASS group. 2. Compile and link the C source code called HIC. You can list its contents with PRINT. The commands to compile and link are given below: CCXLLK source,program,listfile source: source le (HIC) program: compiled, linked code (default = $OLDPASS) listfile: errorlisting le (default = terminal screen) a.
Lesson 1 Introducing Files overwriting the current processed code, you must explicitly specify a program le name in the compile/link command line. Figure 3-5. Overwriting $OLDPASS Allow the name to default to $OLDPASS only if you are working with just one program. Make sure to save $OLDPASS under a di erent name when you nish, because temporary les only exist for the duration of the session! $NULL If you wish your output to \disappear," $NULL is a handy le to use.
Lesson 1 Introducing Files Figure 3-6. $NULL File For example, suppose that you had a program that took user input, performed calculations, and wrote those calculations to the terminal and to a le. During the compiling/linking phase, you are interested only in whether or not the program is syntactically correct. For testing purposes|when you run the program|you are interested only in whether or not it prompts correctly, and lists the results on the screen where you can examine them.
Lesson 4 Using File Equations Lesson 4 Using File Equations Introduction Note Writing le equations Lesson 4 presents the following le concepts: le equations device les formal le designators \backreferencing" le designators You have worked with les that exist permanently or temporarily on disk. What about les that do not really exist, les that are not really les? These are formal les, les whose names are actually \aliases" for other les or devices.
Lesson 4 Using File Equations Note An environment le (ENV) is a special le that contains basic information about page layout and type style. Figure 3-7. File Equations Here are some examples of le equations that you might see on your system. All le equations begin with the keyword, FILE: a. b.
Lesson 4 Using File Equations c. d. e. FILE OUTPUT=TESTFILE;REC=-80,,F,ASCII FILE MAILPRNT;DEV=LP;ENV=ELITE.HPENV.SYS FILE T;DEV=TAPE Q2-10 According to the syntax, in the rst le equation in the example (a), IN is actually an alias for $STDIN. What is $STDIN? Q2-11 In the OUT equation (b), OUT is actually the alias for what? Q2-12 The MAILPRNT equation (d) is used to print HP Desk messages.
Lesson 4 Using File Equations PRINT *OUTPUT You should see the contents of MYJOB1. If you change the le equation and reexecute the PRINT command, you see the contents of another le: FILE OUTPUT=JOB2 PRINT *OUTPUT The le designator, *OUTPUT, does not change, even if the le equation does. In a program, you might wish to change the le equation to redirect output to di erent les or devices. For example, suppose the rst time you run the program, you want the output to go to the screen.
Lesson 4 Using File Equations Teaching exercise 2-4: redirecting output with le equations This exercise provides hands-on experience redirecting output with le equations. 1. Create a le equation for a le designator called OUTPUT. Enter this le equation: FILE OUTPUT=$STDLIST This should direct the output to the standard output device, your terminal screen, whenever you refer to *OUTPUT. 2.
Lesson 4 Using File Equations System-De ned designators When you create le equations, you can use system-de ned le designators, subsystem-de ned le designators, and user-de ned le designators. The system de nes its own set of le designators, some of which were introduced in lesson 3 for programmers: $STDIN $STDLIST $NULL $OLDPASS $NEWPASS Figure 3-9. System-De ned File Designators $OLDPASS and $NEWPASS are the system-de ned temporary les generated during program compiling and linking.
Lesson 4 Using File Equations $STDIN refers to the standard input device, which is, by default, the keyboard. $STDIN is a temporary system le, lasting only for the duration of the session. When writing programs, you can specify that the data be read from the standard input device as follows: FILE TERM=$STDIN . . . read from *TERM $STDLIST refers to the standard output device, which is by default the terminal screen. The output device can also be the line printer.
Lesson 4 Using File Equations User-de ned les You can create your own le equations using a le designator of your choice and an existing device or le of your choice. For example, when you run HP Desk (Hewlett-Packard's electronic mail facility) and enter PRINT, HP Desk assumes that you wish your mail messages printed on MAILPRNT (line printer using special environment le).
Lesson 4 Using File Equations Clearing le equations If you no longer want a le equation to be in e ect, you can use the RESET command to cancel it. The syntax for this command is very simple: RESET filedesignator Q2-16 Be Careful If you no longer want the FILEIN or FILEOUT equations to be in e ect, what do you do? Do not enter RESET @ 4RETURN5 unless you want to cancel all of the le equations in the current session or job. Exercise 2-5: creating and using le equations 1.
Lesson 4 Using File Equations What is the environment le? What does this le equation do? c. FILE INPUT=MYFILE1;REC=-80,,F,ASCII d. FILE OUTPUT=$NULL a. FILE MAILPRNT;DEV=LP HPMAIL PRINT 10 (this is the mail item number) b. FILE OUTPUT=$STDLIST PRINT MYFILE1;OUT=*OUTPUT c. FILE INPUT=$STDIN read FROM *INPUT d. FILE INPUT=MYFILE read FROM *INPUT e.
c. Change the le equation so that the error listing will be stored in a le called ERROR1 with default le characteristics. FILE HIERR=ERROR1 d. Compile and link the program again. Where does the error listing print? e. Change the le equation one more time to store the error listing in the ERROR2 le and compile and link the program. Where does the error listing print this time? Lesson summary 1. System-de ned les that can appear in le equations include the following: a. $STDIN b. $STDLIST c. $NULL 2.
4 Module 3: Batch Processing Module 3 presents the following lessons on using job les: Lesson 1 Introducing Jobs Lesson 2 Examining a Job File Lesson 3 Creating and Streaming a Job File Lesson 4 Monitoring Job Progress Challenge Test 1. Which of the following characteristics refer to batch processing? a. interactive processing b. submits multiple commands at one time c. can be scheduled to run at speci c times d. requires user supervision 2. What are the ve job processing states? 3.
Lesson 1 Introducing Jobs Match the following output spool le states to the correct activity of the spool le: READY Spool le is being printed. PRINT Being created as output. Spool le is ready to print. 8.
Lesson 1 Introducing Jobs Comparison to sessions How well can you distinguish between jobs and sessions? Label each item below to show which refer to jobs and which refer to sessions. Q3-1 More SHOWJOB information Which are characteristics of jobs? Of sessions? a. interactive processing b. synonymous with batch processing c. does not require constant supervision d. submits a single command at a time e. can be scheduled to run at speci ed time f. most time/resource e cient g.
Lesson 1 Introducing Jobs The job is waiting for system resources, or the job limit may have been reached, or the job's priority is too low. EXEC The job is executing. SUSP The job was executing but is now suspended. SCHED The job is scheduled to execute at a time speci ed by the user. Questions 2 through 12 refer to the SHOWJOB display.
Lesson 1 Introducing Jobs Q3-5 Q3-6 If the current jobfence is 7, which of the following jobs will execute? a. JOBA which has an input priority of 7 b. JOBB which has an input priority of 8 c. JOBC which has an input priority of 6 If the current JLIMIT is 5 and ve jobs are executing, what will be the STATE of the next nonscheduled job submitted? JIN and JLIST These two columns show the device (LDEV) numbers assigned to input (JIN) devices and output (JLIST) devices.
Lesson 1 Introducing Jobs SHOWJOB parameters Q3-9 How many jobs and sessions can be run concurrently on this system? Q3-10 According to the JLIMIT information provided, how many more jobs could be executing at this time? Q3-11 How many jobs have been suspended? Q3-12 Which job will be the last to run on 7/20/89? Suppose that you want information about just one job.
Lesson 1 Introducing Jobs Exercise 3-1: lesson 1 review Indicate which of the following statements are true. 1. If the jobfence is 6, jobs must have an input priority of at least 7 in order to execute. 2. When the job limit is reached, the system will not allow you stream any more jobs. 3. The job limit is the maximum number of jobs that can be executing at any one time by the system. 4. Scheduled jobs must also have an input priority above the jobfence in order to execute. 5.
Lesson 2 Examining a Job File Lesson 2 Examining a Job File Introduction Lesson 2 provides the following information about the structure and use of a job le: job commands and how they are used input and output processing and printing priorities Modifying a job le. In this lesson, you will examine a sample job le to see how job les are organized and what kinds of commands are used within these les. Figure 4-1. Examining a Job File Start the editor and list the MYJOB (job) le to your screen.
Lesson 2 Examining a Job File 4 5 6 7 8 9 10 !CONTINUE !EDITOR T MYFILE1 L ALL,OFFLINE EXIT !TELL USERx.ACCTx !EOJ MYJOB1 IS DONE!! Job les are generally created by using an editor or a word processor and may consist of four types of command: MPE/iX batch processing commands other MPE/iX commands user-de ned commands (UDC) and command les (module 5) application commands (optional) You will learn about user-de ned commands and command les in module 5, \UDCs and Command Files.
Lesson 2 Examining a Job File Every job le requires the inclusion of a !JOB command. The purpose of the JOB command is to initiate a batch job. It is always the rst executable line of any job and contains additional information regarding the location of the le materials, user and account names, and so on. (The JOB command is to batch processing what the HELLO command is to interactive processing.
Lesson 2 Examining a Job File Input priority RESTART parameter Note !JOB MYJOB1 . . . ;INPRI=9 . . . Remember the importance of the input priority? The input priority (INPRI) must be greater than the current jobfence in order for a job to execute. What is the input priority for MYJOB? It is 9. If you were going to run MYJOB now on your system, would it run? (Use SHOWJOB to check the jobfence on your system to nd out.) !JOB MYJOB1,USERx/UPASSx . . . ;RESTART; . . .
Lesson 2 Examining a Job File Note SPSAVE parameter Hint: The job listing is a copy of the step-by-step processing of the job. Most users suppress the printing of the job listing unless the job has previously experienced some problems executing. When problems occur, review the job listing to nd where the error(s) occurred. A $STDLIST spool le is generated when you run a job. It is usually destined for the printer when the job has executed.
Lesson 2 Examining a Job File CONTINUE command TELL command and TELLOP command !CONTINUE How do you avoid a job aborting when it encounters an error? The CONTINUE command enables a job to continue to process if it appears immediately before a command line that may cause an error during a job's processing; therefore, the job continues to execute even if an error occurs, and the job listing contains the error message where the error occurred. Look at line 4 in MYJOB.
Lesson 2 Examining a Job File Exercise 3-2: modifying the MYJOB2 le Here's a chance to check your own knowledge about batch processing commands and their use. Suppose that you have been given the following job le (MYJOB2). This job lists the contents of a text le titled MYFILE2; however, the job le needs to be modi ed in order to run correctly. Use the editor to access and list MYJOB2 on your screen. (This le should be in your account.) EDITOR /T MYJOB2 MYJOB2 File 1 2 3 4 5 6 7 8 !JOB MYJOB2,USERx.
Lesson 2 Examining a Job File FROM/Jxx USERx.ACCTx MYJOB2 IS COMPLETE Two sorts of errors can occur the jobs you have been working with. a. The STREAM command detects a signi cant error in the job le itself|a missing or invalid !JOB command; a missing or invalid password; account or groupname; a missing or invalid device speci cation. Such errors will be reported on your screen. If the error is serious, the stream or the job execution may fail. b.
Lesson 3 Creating and Streaming a Job File Lesson 3 Creating and Streaming a Job File Introduction Lesson 3 presents the following MPE/iX job-related tasks: create a job le according to speci cations stream the job so that it runs at a scheduled time, day, or date suspend, resume, and alter a job Abort a job. Up to this point you have worked with existing job les, examining them and modifying them. You will now create your own job les to perform speci c tasks.
Lesson 3 Creating and Streaming a Job File Figure 4-2. Modifying a File 3. Both jobs assume that the current jobfence is 7 and the outfence is 7. Any job with an output priority of 3 to 5, inclusive, will print after hours, when most of the employees have gone home. 4. Create JOB1 according to the following \skeletal" job le so that it performs the speci ed functions. Note Each letter refers to a function listed below the \skeletal" job le. The rst three lines are the editor comments.
Lesson 3 Creating and Streaming a Job File g h i j L ALL,OFFLINE EXIT ! ! 5. In your JOB1 le, complete lines a, b, d, e, f, g, h, i, and j of JOB1 to do the following: a. Specify an input priority high enough to guarantee that the job runs immediately. This means that the input priority must be above the current JOBFENCE (7). b. Suppress the printing of the job listing on the printer (LP). This means that the OUTCLASS priority (1) is less than the current OUTFENCE (7).
Lesson 3 Creating and Streaming a Job File Figure 4-3. JOB1 File 7. Using your JOB2 le, create JOB2 according to the \skeletal" job le below so that it performs the speci ed functions. Note Each letter refers to a function listed below the \skeletal" job le. The rst three lines beginning with << are the editor comments. They do not belong in any job le you create.
Lesson 3 Creating and Streaming a Job File a. Specify an input priority that guarantees that the job runs now. This means that the input priority (9) is above the current JOBFENCE (7). b. Suppress the printing of the error/job listing on the printer (LP). This means that the OUTCLASS priority (5) is less than the current OUTFENCE (7). Ensure that the job will restart in the event of a system halt. c. Run the editor. d. Text in a le called MYFILEM. e.
Lesson 3 Creating and Streaming a Job File Streaming a job Note Now that you have had the chance to create job les on your own, let's learn what you can do to get those jobs to execute. The process of doing this is called streaming a job. This is accomplished with the STREAM command. The STREAM command has options that allow you to actually specify the time and date that you wish a job to run. Before you stream a job, check the job le to make sure that the user and account passwords are correct.
Lesson 3 Creating and Streaming a Job File See the following gure for examples of the various options. These options are explained in depth in the MPE/iX Commands Reference Manual Volumes 1 and 2 (32650-90003 and 32650-90364) and in the Help facility, under the STREAM command. Figure 4-5. STREAM Command Options If you specify a job start at 3:00 pm (15:00) and it is now 3:01 pm, your job will start at 3:00 pm the next day. For a greater understanding of these options, study the following examples: 1.
Lesson 3 Creating and Streaming a Job File Q3-26 Command 1. STREAM JOBFILE a. 2. STREAM JOBFILE ;AT=8:00 STREAM JOBFILE ;AT=20:00 STREAM JOBFILE ;IN=,+8 STREAM JOBFILE ;IN=+1,+8 b. STREAM JOBFILE ;DATE=08/09/89 ;AT=20:00 STREAM JOBFILE ;DAY=MONDAY ;AT=22:00 STREAM JOBFILE ;DATE=08/09/89 f. 3. 4. 5. 6. 7. 8. Q3-27 Aborting a job c. d. e. Description Job will run on Monday, at 10:00 P.M. Job will run on August 9, at 8:00 P.M. Job will run today, at 8:00 A.M. Job will run immediately.
Lesson 3 Creating and Streaming a Job File Note the resulting job number that displays after you enter the command. Verify that the job is processing by entering the following command (note the job number): SHOWJOB Now abort the job using the job number and do a SHOWJOB again to verify that the job no longer exists. Note Sometimes ABORTJOB takes a few seconds to abort a job. Consequently, you may have time to execute a SHOWJOB and see your job still listed. Do not be surprised if that happens.
Lesson 3 Creating and Streaming a Job File RESUMEJOB command. Jobs that are suspended are listed as being in the SUSP state when you do a SHOWJOB. Figure 4-6. Resuming or Aborting Jobs Note You can suspend a job only if it is your job and the system operator has set JOBSECURITY to LOW (or the operator issues the ALLOW command so that you can issue BREAKJOB). Q3-30 Q3-31 Altering a job To test the BREAKJOB command, please STREAM JOB1. Allow the job to process by waiting about 10-15 seconds.
Lesson 3 Creating and Streaming a Job File currently in the EXEC state. You must be in the INTRO, WAIT, or SCHED state. To terminate JOB1, abort it: ABORTJOB #Jxxx Now, return to the editor and modify the JOB1 le so that the input priority is reduced to 1. Keep the le and restream JOB1: STREAM JOB1 Note You can alter a job only if it is your job and the system operator has set JOBSECURITY to LOW (or the operator issues the ALLOW command so that you can ALTJOB).
Lesson 4 Monitoring Jobs Lesson 4 Monitoring Jobs Introduction Lesson 4 presents the following command: LISTSPF and SPOOLF. These commands let you monitor job progress: You had the opportunity in the last lesson to STREAM jobs that were scheduled to run at various times, or that were purposely set not to print (deferred priorities). Now you will monitor the progress of the jobs and look at the job listings of your completed jobs. This allows you to determine whether or not the job was successful.
Lesson 4 Monitoring Jobs #O1585 J172 $STDLIST 1 1 LP CREATE INPUT SPOOL FILES ACTIVE = 0; OPEN = 0; READY = 0; OUTPUT SPOOL FILES CREATE = 1; DEFER = 0; DELPND = 0; PRINT = 0; PROBLM = 0; TOTAL IN FILES = 0; IN SECTORS = 0; TOTAL OUT FILES = 1; OUT SECTORS = 2048; USER1.ACCT1 READY SELECTED SPSAVE XFER = = = = 0; 0; 0; 0 OUTFENCE = 7 OUTFENCE = 7 FOR LDEV 6 Note the les associated with the JOB1 job number. In this example, the JOB1 job number is #J172.
Lesson 4 Monitoring Jobs Heading SPOOLID JOBNUM FILEDES DEV PRI COPIES STATE RSPFN OWNER De nition A spool le number|also called a spool le ID number (typically there is more than one spool le per job): Input les begin with \I". Output les begin with \O" Job number. The le designator for the spool le. Device where spool le will eventually be printed. Output priority.
Lesson 4 Monitoring Jobs Where spool les are kept MPE/iX has one system account that holds most commonly generated spool les: HPSPOOL. Input spool les are found in the IN group. Output spool les are found in the OUT group. Q3-34 How many les are associated with JOB1? What are they called? More detailed information about your spool les is available with the ;DETAIL option of the LISTSPF command.
Lesson 4 Monitoring Jobs For JOB1, $STDLIST should be READY when approximately 13144 lines have been written to it (all CHANGEs complete). At this point, do a LISTSPF, and an entry for EDTLIST may appear: SPOOLID JOBNUM FILEDES PRI COPIES DEV STATE RSPFN OWNER #O1585 #O1585 J172 J172 EDTLIST 8 $STDLIST 1 INPUT SPOOL FILES ACTIVE = 0; OPEN = 1; READY = 0; 1 1 LP LP READY CREATE OUTPUT SPOOL FILES CREATE = 1; DEFER = 0; DELPND = 0; PRINT = 0; PROBLM = 0; TOTAL IN FILES = 1; IN SECTORS = 36; USER1.
Lesson 4 Monitoring Jobs Press 4RETURN5 each time you want to see another 23 lines of the le. If instead you want to see a particular line, enter that line number and press 4Return5: (24/340) Continue? 3014Return5 In this example, PRINT displays line 301 and the next 22 lines following it. You can jump forward by 40 lines by entering +40; or jump backward by 40 lines by entering -40. If you do not want to see more of the le, enter N (for No) and press 4Return5.
Lesson 4 Monitoring Jobs Figure 4-7. Spool Files EDTLIST Output from the Editor Note Normally, if serious errors were indicated in $STDLIST, you would purge the spool le, return to the original job le, and correct the lines that were speci ed in the job listing. Then you would stream the job again. Because the warnings were not serious (truncations), you need not correct them. You cannot use PRINT or the editor to look at the input spool le ($STDIN), since it is a private spool le.
Lesson 4 Monitoring Jobs You have just altered the output priority from 5 (below the OUTFENCE), to 9 (above the OUTFENCE), and the le should be ready to print. LISTSPF filenumber If the state is PRINT, it is printing. If the state is READY, is not printing. Continue checking the status. Q3-36 What happens when the spool le is no longer active on the printer? As you may have noticed, the PRINT command gives you a way to determine if your processed job le had any errors.
Lesson 4 Monitoring Jobs Aborting jobs What happens if you check a job's progress, and decide that the job has a serious problem? Unfortunately, you cannot use the editor at that point to examine the error/job listing when the job is still executing and its listing spool le is in the CREATE (not READY) state; however, you can use PRINT O< lenumber>.OUT.HPSPOOL to display the spool le while it is still in the CREATE state.
Lesson 4 Monitoring Jobs Figure 4-8. and Aborted Jobs EDTLIST Output from the Editor SPOOLF Typically at this point, you would note where errors occurred. You could then purge the spool les, return to the editor, and make the necessary corrections to your job le. Please purge any remaining output spool les now: SPOOLF @;SELEQ=[OWNER=USERx.
Lesson 4 Monitoring Jobs Warning SPOOLF is a powerful command. Be certain of what you are doing when you use it. If you have AM capability, SPOOLF @;DELETE will delete all of the spool les in the account. If you have SM or OP capability, or if you are working at the console, SPOOLF @;DELETE will delete all spool les on the system. 6. Check to see if you have any additional spool les (LISTSPF @). These are probably associated with previously suspended or scheduled jobs. Please purge them now.
g. The SPOOLF lenumber;DELETE command deletes the speci ed spool le. Warning 4-38 Module 3: Batch Processing SPOOLF is a powerful command. Be certain of what you are doing when you use it. If you have AM capability, SPOOLF @;DELETE will delete all of the spool les in the account. If you have SM or OP capability, or if you are working at the console, SPOOLF @;DELETE will delete all spool les on the system.
5 Module 4: File Transfer and Storage Module 4 presents lessons on transferring les using FCOPY and STORE/RESTORE. Lesson 1 Using FCOPY Lesson 2 Storing and Restoring Files Challenge Test 1. What FCOPY command would you use to copy the le MYJOB1 from the PUB group to the CLASS group and not overwrite a le with the same name in the CLASS group? 2. What FCOPY command would allow you to copy the STATS le from the PUB group in the ADVUSER account to the CLASS group in your account, ACCTx? 3.
Lesson 1 Using FCOPY Lesson 1 Using FCOPY Introduction Lesson 1 presents the following information on FCOPY: Comparison to COPY command. Copying les within and across accounts. Appending les. Copying les to and from other devices. Figure 5-1. FCOPY You have probably used the COPY command for copying les within an account.
Lesson 1 Using FCOPY FCOPY: FCOPY FROM=filename;TO=filename Notice the locations of the equal signs (=) following the words FROM and TO. Many users make mistakes here. The FROM information tells your system the name of the source le and its location. The TO information tells the system the name of the new or destination le and its location. Adding the NEW option at the end of the FCOPY command assures you that the command will not copy the le over a previously existing le with the same name.
Lesson 1 Using FCOPY If you get an error message If you got a syntax error, check your FCOPY command again to be sure that you have entered the command correctly. *54* SYNTAX ERROR If the syntax error message appeared, check the equal sign (=) after the FROM and TO, and the semicolon (;) before the TO. *144* NEW OPTION: FILE ALREADY EXISTS If this NEW option error message appears change the new name for your le to MYJOB3 in your FCOPY command.
Lesson 1 Using FCOPY RELEASE MYJOB1 Step 2. If you are not already logged on to your own account, log on now. Step 3. Enter the following FCOPY command on your keyboard substituting the other student's account name for ACCTx. FCOPY FROM=MYJOB1.PUB.ACCTx;TO=MYJOB1.PROJECT;NEW Step 4. Errors? Check your syntax and reenter. Check the next section, \Problems," if needed. Step 5. Use the LISTFILE command to make sure the le transfer was completed successfully. LISTFILE MYJOB1.PROJECT Step 6.
Lesson 1 Using FCOPY Exercise 4-2: appending one le to another There will be times when you want to append several les together. FCOPY can do this by creating a new le and then appending additional les to this le. In this exercise you will combine JOB1, JOB2, JOB3, and JOB0 in a single JOBX le. 1. Determine the total number of records used by each le using LISTFILE, 1. Add these together.
Lesson 1 Using FCOPY Copying les from disk to other devices To use the FCOPY command to copy les from disk to other devices (such as tape or peripherals), you must do the following: Use a FILE command to de ne a le name for your device. For example, assign the name LIST to the line printer (LP). FILE LIST;DEV=LP Use the device's lename as the TO lename. Precede the le name with an asterisk to backreference it. FCOPY FROM=MYJOB1.CLASS.
Lesson 1 Using FCOPY Lesson summary 1. The FCOPY and COPY commands are very similar in syntax; however, FCOPY uses the NEW option to prevent overwriting a le; COPY uses a NO option. COPY FROM=MYFILE;TO=MYFILE.PUB;NO FCOPY FROM=MYFILE;TO=MYFILE.PUB;NEW 2. Both FCOPY and COPY allow you to copy a le from another account to your current account. You issue the respective command from the destination account and fully qualify the source le name. FCOPY FROM=MYFILE.PUB.ACCTx;TO=MYFILE;NEW 3.
Lesson 1 Using FCOPY Exercise 4-3: lesson 1 review 1. Note which tasks you are required to do when copying les: Tasks a. b. c. d. e. f. g. h. Within Within Account Device to Group Account to Account Device Release le before copying. De ne the device le(s). Fully qualify the le names ( le.group.account). Backreference device le names with asterisks. Require only the FROM lename and the TO lename. Be in the destination account when you issue the FCOPY command. Secure the le after copying.
Lesson 2 Storing and Restoring Files from Tape Lesson 2 Storing and Restoring Files from Tape Introduction Note Lesson 2 presents the STORE/RESTORE utility: using STORE to copy les to tape using RESTORE to copy les from tape to a system Figure 5-2. STORE/RESTORE Utility Subsystem The user procedures established by system management for storing and restoring les to and from tape may vary from facility to facility.
Lesson 2 Storing and Restoring Files from Tape project will be resumed in one year. How can you store the les on tape now, and then reload them on disk when the project resumes? Sooner or later you will encounter similar situations where you will need to store les on tape for immediate or future use. The most e cient way to store les for possible future use or to transport les between accounts is by using the STORE/RESTORE utility.
Lesson 2 Storing and Restoring Files from Tape >> TURBO-STORE/RESTORE VERSION A.21.01 (C) 1986 HEWLETT-PACKARD CO. (TODAY'S DATE, TIME) FILES STORED : Q4-5 Transporting les to a new system HP30319A << 19 How would you change the preceding STORE command to copy all the les in your account to a tape as in scenario 3? Sometimes it is necessary to use STORE in order to transport les to another HP 3000 system.
Lesson 2 Storing and Restoring Files from Tape STORE parameters Hint Besides the TRANSPORT parameter, the STORE command has a number of other parameters, which allow you to copy di erent sets of les as well as monitor the progress of the STORE process. Go into the Help Facility now and list the STORE parameters to your screen. Your awareness of the additional capabilities of this command is important for future use. HELP STORE PARMS Several of the parameters are discussed below.
Lesson 2 Storing and Restoring Files from Tape Q4-7 Lesson summary What RESTORE command would restore only the les from the PROJECT group of your account? 1. To store les on tape, use a le equation to de ne the destination device. Use a STORE command so that the name(s) of the le(s) to be stored is backreferenced to the tape: FILE T;DEV=TAPE STORE filename;*T 2. Add the TRANSPORT parameter to your STORE command if the STORE tape will be reloaded on a system other than MPE/iX: STORE @.
Lesson 2 Storing and Restoring Files from Tape The tape density of the current system is 6250 bpi; however, the tape drives for the new system will accommodate only 1600 bpi tape. How would you write the le equations and the STORE and RESTORE commands to complete the process? 4. Another member of the department used the PURGE parameter when storing les on tape. Unfortunately, the tape has proven to be defective.
6 Module 5: User Commands Module 5 presents the following lessons on user commands, including command les and UDCs: Lesson 1 Comparing UDCs and Command Files Lesson 2 Understanding Search Priorities Lesson 3 Cataloging UDCs Lesson 4 Using UDC Options Lesson 5 Using UDC Parameters Lesson 6 Using the Command Interpreter Challenge Test 1. TRUE OR FALSE: To execute a command le, you must enter its le name. 2. TRUE OR FALSE: To execute a UDC, you must enter its le name. 3.
Lesson 2 Storing and Restoring Files from Tape *** PR PARM FILE1=MONEY,FILE2="$NULL",FILE3="$NULL" PRINT !FILE1 PRINT !FILE2 PRINT !FILE3 *** a. What happens when you enter this command: PR b. What happens when you enter this command: PR DOLLARS,CENTS 11. What does the following UDC do when you enter this? FILEX,2 LSF UDC: LSF MYFILE1,OPTION LISTFILE !MYFILE1,!OPTION 12.
Lesson 1 UDCs and Command Files Lesson 1 UDCs and Command Files Introduction Lesson 1 presents a review of command les and an introduction to UDCs. You will learn how to: distinguish between command les and UDCs print a UDC le and a UDC ensure that a UDC goes into e ect at logon Note In order to complete the exercises in this module, you need to be in the CLASS group of your account.
Lesson 1 UDCs and Command Files Comparison of command les and udcs Consider how the command les listed previously would appear as UDCs in a UDC le, MYUDC1. Figure 6-1. Command Files vs UDC File Some of the di erences you will notice are: Command le names (SHOW and SC) are not part of the command le. UDC names (SHOW and SC) are part of their respective UDCs and are referred to as command header names. UDCs are invoked by their command headers. Individual UDCs are separated by asterisks within a UDC le.
Lesson 1 UDCs and Command Files Why use a UDC le for user commands? Listing UDC les Despite the added e ort to create and catalog UDC les, they provide some features unavailable with command les. One advantage is the order of execution. Commands stored in a UDC le execute before those stored in a command le. (You will learn about search and execution priorities in Lesson 2.) Another important advantage is that UDCs can use a logon option that allows the UDC to execute immediately upon the user's logon.
Lesson 1 UDCs and Command Files SHOWCATALOG *** SM SHOWME *** SJ SHOWJOB *** As mentioned earlier, UDC les may contain one or more UDCs with the individual UDCs separated by asterisks. (Remember? No asterisks are included in command les.) How many UDCs are in MYUDC1? If you said ve, you're right. STARTUP, SETEQ, SHOWCAT, SM, and SJ are the ve UDCs contained in MYUDC1. UDC characteristics Each UDC begins with its command header or UDC name, for example, STARTUP, followed by commands to be executed.
Lesson 1 UDCs and Command Files Lesson summary 1. UDCs and command les share a number of features; however, unlike command les, UDCs are stored in a UDC le, which must be cataloged before the UDCs may execute. 2. Use the following commands to get information about UDC les and UDCs stored in your account: SHOWCATALOG Displays cataloged UDC les PRINT udcfilename Displays contents of a UDC le HELP udcname Displays contents of a UDC Exercise 5-1: lesson 1 review 1.
Lesson 1 UDCs and Command Files d. Which of the following are command headers in the example above? SM SHOWCAT MYCOMM2 MYCOMM1 BEGIN SHOWME 3. Select the correct command to do each of the following: Function a. b. c. PRINT HELP SHOW UDC Name CATALOG Filename List all UDC les currently cataloged for an account. List the contents of a speci ed UDC. List the contents of a speci ed UDC le.
Lesson 2 Understanding Search Priority and Search Path Lesson 2 Understanding Search Priority and Search Path Introduction This lesson presents information on the following topics: MPE/iX search priorities the use of the XEQ command To be sure that your user commands execute, you need to be aware of how MPE/iX interprets what is entered at the prompt.
Lesson 2 Understanding Search Priority and Search Path Figure 6-3. MPE/iX Search Priority UDC directory Suppose you were to enter the following at the MPE/iX prompt: TRYIT The system would rst search for TRYIT in the directory of UDC les. (This directory is where all cataloged UDCs are kept.) User created UDCs are searched rst, account UDCs next, and system UDCs last. If TRYIT were a UDC, the search would end and TRYIT would be executed.
Lesson 2 Understanding Search Priority and Search Path Q5-1 Command directory But what if TRYIT were not found in the UDC directory? Then the search would continue to see if TRYIT were in the MPE/iX command directory If it were, the system would execute it. Q5-2 File directory Which UDC in each of the following pairs would execute? 1. the user UDC SM or the system UDC SM? 2. the system UDC LF or the account UDC LF? 3.
Lesson 2 Understanding Search Priority and Search Path Search path Figure 6-4. Search Path Since the le name TRYIT has not been quali ed, the system follows a designated search path looking for a matching name. By default, the system rst looks in your current group, next in your PUB group, and nally in PUB.SYS. If TRYIT were not found in the search path or were found to be a nonexecutable le, the system would issue an Error Message and return you to the MPE/iX prompt.
Lesson 2 Understanding Search Priority and Search Path Entering XEQ MYFILE ensures that your program le MYFILE executes. Lesson summary Note 1. MPE/iX interprets everything entered at the prompt to be a command and prioritizes its search for that command as follows: a. UDCs rst b. MPE/iX commands second c. le names last 2. Use the XEQ command to ensure that the system executes a command or program le having the same name as a cataloged UDC.
Lesson 3 Cataloging UDCs Lesson 3 Cataloging UDCs Introduction Reviewing UDCs Lesson 3 covers the following topics dealing with cataloging UDCs for use: cataloging process SETCATALOG command APPEND option of SETCATALOG DELETE option of SETCATALOG uncataloging UDCs Before you begin cataloging UDCs, see how much you remember.
Lesson 3 Cataloging UDCs Now execute the CHPUB command le. Do a SHOWME to verify that you are in the PUB group. Change back to your CLASS group. You can use the MPE/iX CHGROUP command, or create another command le named CHCLASS to do this. Enter: CHGROUP CLASS Since the CHPUB and CHCLASS commands work, you can add them to one of your UDC les. Do a SHOWCATALOG to see what UDC les are currently cataloged. To add the command to MYUDC1, you have to uncatalog MYUDC1.
Lesson 3 Cataloging UDCs only removes the UDC les from the UDC directory; it does not purge them from the system. Do a SHOWCATALOG to verify that no UDC les are currently cataloged. Now catalog only the MYUDC2 le: SETCATALOG MYUDC2 Adding UDC les When using the SETCATALOG command you must specify all the UDC les you wish to put in the UDC directory. Each time you use the SETCATALOG command, any UDC les speci ed replaces those currently in the UDC directory.
Lesson 3 Cataloging UDCs Deleting UDC les without parameters removes all of your UDC les from the UDC directory. Suppose you want to remove and edit just one of your UDC les? Use the ;DELETE option of the SETCATALOG command. SETCATALOG SETCATALOG UDCfilename;DELETE You may remove one or more UDC les from the catalog. To remove more than one, use this form: SETCATALOG UDCfilename1, UDCfilename2...
Lesson 4 Using UDC Options Lesson 4 Using UDC Options Introduction Lesson 4 presents the following options associated with UDCs: LOGON/NOLOGON LIST/NOLIST HELP/NOHELP RECURSION/NORECURSION PROGRAM/NOPROGRAM'' BREAK/NOBREAK These options a ect the way that the UDC is used and the way that it acts. Typically, the option must be speci ed in the line directly after the UDC header (name). Several of these options can also appear within the body of the UDC. (This is discussed later in this lesson.
Lesson 4 Using UDC Options SHOWTIME *** ST2 OPTION NOLIST SHOWTIME *** Note HELP/NOHELP option Verify that MYUDC2 is still cataloged. If it is not, please use SETCATALOG to do so. Execute ST1 and ST2. What happens? Notice that with ST1, both the MPE/iX command (SHOWTIME) and its results are displayed on the screen. With ST2, only the results of SHOWTIME are displayed. ST1 has the LIST option, and ST2 does not. Normally, you don't need a listing of the actual commands in the UDC.
Lesson 4 Using UDC Options RECURSION/ NORECURSION option Normally, in your UDC le you can use a UDC within the de nition of another UDC, only if the one you are referencing appears after the one you are currently using. For example, this is a valid UDC sequence within a UDC le: UDCFILE1: LOGON command command command ********** UDC1 command UDC2 command ********** UDC2 command command command *********** is called within UDC1, and that is acceptable because UDC2 is de ned after UDC1 in UDCFILE1.
Lesson 4 Using UDC Options By specifying the RECURSION option after the UDC header, you can reference any UDC in the UDC directory, even if it was de ned in a UDC le that was cataloged prior to the current one.
Lesson 4 Using UDC Options SHOWME *** SO SHOWOUT *** ********* End of Exercise 5-3 ********* Because recursion allows two UDCs to call each other and enables a UDC to call itself, limitations have been put in place to prevent endless loops. The maximum number of times that a UDC can call itself, or that two user commands can call each other is 30 total times. When that maximum is reached, the system interrupts the process with an error message. This is a system-imposed restriction.
Lesson 4 Using UDC Options The default is OPTION PROGRAM. However, even with OPTION PROGRAM, some subsystems and utilities won't recognize UDCs, depending on how they were programmed. Note The PROGRAM/NOPROGRAM option must appear after the UDC header and the PARM line.
Lesson 4 Using UDC Options Note Position of options The BREAK/NOBREAK option must appear immediately after the UDC header. By now you've probably noticed that most options appear on the lines following a UDC header, or on the rst lines of a command le. There are two options that can appear both after the UDC header and in the UDC body. What are they? OPTION RECURSION/NORECURSION OPTION LIST/NOLIST When an option appears within the body, it takes precedence over the option in the header.
Lesson 4 Using UDC Options Figure 6-6. Default Options Exercise 5-4: UDC options Note 1. Add a single UDC called SLS to the MYUDC2 le. Have the UDC do the following in the order given: a. Execute the SHOWTIME command without listing the SHOWTIME command on the screen. b. Execute the LISTFILE command without listing the LISTFILE command on the screen. c. Execute the SHOWME command and list the SHOWME command on the screen. Make sure that you uncatalog MYUDC2 before adding SLS to it. 2.
Lesson 4 Using UDC Options Lesson summary Note 1. The following options control what you can do with your UDCs and command les (only LOGON/NOLOGON and RECURSION are valid only for UDCs): a. LOGON/NOLOGON - determines whether or not the UDC goes into e ect automatically upon logon (default = NOLOGON). b. LIST/NOLIST - determines whether or not the commands making up the UDC, as well as its results, are listed when the UDC is executed (default = NOLIST). c.
Lesson 5 Using Parameters Lesson 5 Using Parameters Introduction Lesson 5 presents the following information about UDC and command le parameters: parameter de nition. correctly using required and optional parameters. correctly specifying parameters in UDCs and command les. Passing values by parameters You may have noticed, when examining the MYUDC2 le, that some UDCs have more than just a command name in the header. Some also have parameters.
Lesson 5 Using Parameters Figure 6-7. Parameters in a UDC Command File Example: Figure 6-8. Parameters in a Command File In these examples, FILE is the parameter. The user command name is PR. The syntax of this user command indicates that PR must always be followed by a value. This value will be some le name supplied by the user. The system knows that FILE is a parameter because of the PARM line.
Lesson 5 Using Parameters Figure 6-9. PR Command File Try it and see! What happens if you just type: PR You get an error because, according to the UDC de nition, the system expects a value after the PRINT command. In this lesson you will learn how to avoid such errors by de ning default parameter values. What if you wanted to print several les? What happens if you type: PR JOB1,JOB2 Once again, you get an error because, according to the UDC de nition, only one parameter value is expected.
Lesson 5 Using Parameters FILE1 PARAMETER IS REQUIRED. PARAMETERS DO NOT MATCH USER COMMAND DEFINITION. SETCAT UDC Example: SETCAT UDCFILE="MYUDC1" SETCATALOG !UDCFILE *** Note Explanation: The purpose of this UDC is to catalog a speci ed UDC le. The exclamation point (!) tells the system that when you execute the SETCAT user command, the le name that you specify is to be passed to the parameter, UDCFILE. UDCFILE is an optional parameter.
Lesson 5 Using Parameters Figure 6-10. PRX Command File PRX Command File: PARM FILE1=$NULL,FILE2=$NULL,FILE3=$NULL PRINT !FILE1 PRINT !FILE2 PRINT !FILE3 Explanation: The command in the previous gure lets you print up to three les. All three parameters default to $NULL (the system designator for an empty le), so that only a $NULL value with no data is passed to them. In this example, assigning a parameter value of $NULL, no error message results if you forget to specify a value for that parameter.
Lesson 5 Using Parameters SETCATX UDCFILE1="MYUDC1",UDCFILE2=$NULL,UDCFILE3=$NULL SETCATALOG !UDCFILE1,!UDCFILE2,!UDCFILE3 *** Explanation: The UDC in the gure above lets you catalog up to three les. The rst parameter defaults to MYUDC1. The second and third parameters default to $NULL (empty le). To test how the SETCATX UDC works with one or more values, start by cataloging only MYUDC2: SETCATX MYUDC2 Do a SHOWCAT to verify that only MYUDC2 is cataloged. So, SETCATX works with only one value.
Lesson 5 Using Parameters Bene ts of parameters Putting parameters in your UDCs can provide a short-cut method for entering lengthy commands that change frequently. For example, suppose that you run a program that writes its results to *OUT. You must change the OUT le equation each time you run the program so that the output goes to one of three di erent les: OUTFILE1, OUTFILE2, and OUTFILE3.
Lesson 5 Using Parameters Note When using parameters in a UDC, it's a good idea to create a command le rst and test it, and then convert it to a UDC. 2. Test and execute LS on le JOB1 as follows: a. Enter LS without any numeric option value. What happens? b. Enter LS with parameter value 1; then with parameter value 2; then with parameter value 3. 3. When the LS command le is working, convert it to a UDC and add it to MYUDC3. This time, do not use the PARM line.
Lesson 6 The Command Interpreter Lesson 6 The Command Interpreter Introduction Note Lesson 6 presents two basic uses of the command interpreter: toggling between an editor and the operating system when compiling and linking a program toggling between an editor and the operating system when testing a command le This lesson is primarily for programmers and system managers. You can skip the lesson if you perform neither programmer nor system manager functions.
Lesson 6 The Command Interpreter You can enter SHOWVAR HPCIDEPTH to learn your CI level. When CI is run from the editor, HPCIDEPTH=2. The main CI level (root) is HPCIDEPTH=1 . To run the CI, enter the following command at the editor prompt (/): :RUN CI.PUB.SYS or :XEQ CI To exit the CI and return to the editor, enter: EXIT Figure 6-13. The CI To demonstrate the assistance that the CI can provide you during program development, follow along with the teaching exercise below.
Lesson 6 The Command Interpreter Teaching exercise 5-6 for programmers: using the command interpreter 1. There is a C program in your ACCTx account and CLASS group called HIC. You will be compiling, linking, modifying, and running the program using the CI and the editor. It purposely has some hidden bugs in it so that it does not compile successfully the rst time that you try to do so. 2. First, compile and link the program using the command line shown below: CCXLLK HIC,HICP where: a.
Lesson 6 The Command Interpreter 5. Run the program by entering the following: HICP 6. The program should prompt you for your logon user name, and then print out the following message: Enter your user name> HELLO user name WELCOME TO THE MPE/iX ADVANCED SKILLS COURSE!!! YOUR CURRENT SEARCH PATH is *** TODAY IS date. GOOD LUCK! 7. Return to the editor by entering: EXIT You should see the editor prompt (/). a. Type: LIST 80/LAST b.
Lesson 6 The Command Interpreter 2. First, execute the command le by entering the following: HICOM Note An error message results. Eventually, you will have to modify the source code and correct the errors so that the program will run without error. 3. Edit the command le, make the necessary changes, and save the le.
!HPPATH This indicates that a text string showing the value of HPPATH is to be displayed. HPPATH is a system variable that you will learn about in the \Variables and Expressions" module. c. Keep the le and then use the CI again to execute the command le. The message that you receive should now display a search path. You can also execute the command le by entering :XEQ HICOM d. Return to the editor and then leave the editor EXIT to nish.
7 Module 6: Variables and Expressions Module 6 presents the following lessons on using variables and expressions in command les and UDCs: Lesson 1 Understanding Variables Lesson 2 Using Variables and Expressions Challenge Test 1. Which of the following is a legal variable name: a. VAR_1 b. VAR-1 c. VARIABLE#1 d. VARIABLE_1 e. VAR 1 f. 1_VAR 2. Which of the following system-de ned variables have values that can be altered? a. HPPROMPT b. HPJOBLIMIT c. HPSESLIMIT d. HPPATH 3.
8. Which series of statements is correct for prompting a user for an integer value (VAR_A), adding 2 to that value, assigning the result to VAR_B, and then displaying VAR_B? a. INPUT VAR_A;PROMPT="What is the value of variable A? SETVAR VAR_B,VAR_A + 2 SHOWVAR VAR_B INPUT VAR_A;PROMPT="What is the value of variable A?" SETVAR VAR_B,!VAR_A + 2 SHOWVAR VAR_B b. c. INPUT VAR_A;PROMPT="What is the value of variable A? " SETVAR VAR_A,!VAR_A SETVAR VAR_B,VAR_A + 2 SHOWVAR VAR_B 9.
Lesson 1 Understanding Variables Lesson 1 Understanding Variables Introduction Lesson 1 covers the following topics dealing with variables and how to de ne them: how to create user-de ned variables how to modify user-de ned and some system-de ned variables SETVAR SHOWVAR DELETEVAR As you become more experienced, you will probably nd yourself creating more and more specialized user commands. In doing so, you will probably nd the use of variables invaluable.
Lesson 1 Understanding Variables LF command le: This command le lets you list the names and characteristics of all les in a speci ed group and account, using LISTFILE,1 or LISTFILE,2 or LISTFILE,3 commands. SETVAR FILENAME,"//" SETVAR RESPONSE,"N" SETVAR OPTION,"1" INPUT RESPONSE;PROMPT="DO YOU WISH TO LIST ANY FILE(S)? (Y OR N): " WHILE RESPONSE='Y' DO INPUT FILENAME;PROMPT="ENTER FILE.GROUP.
Lesson 1 Understanding Variables ACCT = ACCTx Note Either single or double quotation marks may be used. In special cases, you must use double quotes.
Lesson 1 Understanding Variables HPJOBCOUNT Examples of invalid names are: #$%& MAX# ERROR_# error flag 123 If you look in the two command les, you will see these variables: STATS le: LF le: HPJOBLIMIT HPJOBCOUNT Q6-1 Variable types RESPONSE FILENAME OPTION Which of the following are acceptable names for variables? a. $DOLLARS b. CIERROR c. FRED_FLINTSTONE d. HPINPRI e. RINGO* f. _JAMES_BOND g.
Lesson 1 Understanding Variables Note Variables cannot have real number values. For example, 100000 is an acceptable value for the SALARY variable because it is an integer value. 100000.00 is not an acceptable value for the SALARY variable because it is a real value. Decimal points are not allowed in any numeric variable value. boolean value is TRUE or FALSE.
Lesson 1 Understanding Variables HPSESLIMIT HPPROMPT HPPATH HPVERSION HPUSER HPSESCOUNT Q6-3 YES NO NO YES YES YES NO YES YES NO NO NO Use the Help facility to look up each of these variables. What do each of these variables do? What are their current values? Hint: Use SHOWVAR to display the value of each.
Lesson 1 Understanding Variables Q6-5 Q6-6 User-de ned variables What are the system-de ned variables in the STATS command le? Are those variables user-modi able? User-de ned variables are variables with names and values that the user speci es. Once again, names must follow standard conventions. You can read, modify, or delete any user-de ned variable. User-de ned variables are session dependent. They are good only for the one user during that one session.
Lesson 1 Understanding Variables Exercise 6-1: variables 1. De ne a variable called MYPROMPT and assign it the value currently stored in HPPROMPT. 2. Display the value of MYPROMPT. 3. Delete MYPROMPT. Verify that it is gone. Try to delete HPPROMPT. Why can you delete MYPROMPT, but not HPPROMPT? ********** End of Exercise 6-1 ********** Lesson summary 7-10 1. System-de ned variables have system-assigned names and values. Some of them have values that can be modi ed by the system manager.
Using Variables and Expressions Lesson 2 Using Variables and Expressions Introduction Lesson 2 presents the following information about how the variables can actually be used, once they have been de ned: assigning values to variables both interactively and with programs displaying and manipulating variable values by using expressions Using variables in the STATS command le Look at how the variables HPJOBLIMIT and HPJOBCOUNT are used in this command le.
Using Variables and Expressions Implicit dereferencing. This does not involve an exclamation point. It is done automatically, without an exclamation point. Implicit deferencing occurs in the commands SETVAR, IF-THEN-ELSE-ENDIF, WHILE-ENDWHILE, and CALC. (You will look at IF-THEN-ELSE-ENDIF and WHILE-ENDWHILE later in this lesson.
Using Variables and Expressions Q6-9 In an earlier lesson you de ned three variables, USER, GROUP, and ACCT. How would you de ne them again if they were to be given the same values as those currently stored in the system-de ned variables, HPUSER, HPGROUP, and HPACCOUNT? SETVAR USER, SETVAR GROUP, SETVAR ACCT, Note You may explicitly dereference a variable in a statement that requires only implicit dereferencing. Now look at another case where no exclamation point is necessary, the IF-THEN-ELSE statement.
Using Variables and Expressions Figure 7-2. IF-THEN-ELSE-ENDIF Statement IF condition is true THEN take this action ELSE take a different action ENDIF Note that IF is followed by an optional THEN. ELSE is optional and can be included if you have another choice. ENDIF must \close" the IF statement. IF, ELSE, and ENDIF keywords are not indented, but actions associated with THEN and ELSE are indented. This helps improve readability, but is not required.
Using Variables and Expressions Q6-10 According to the IF-THEN statement in the STATS le, what message is displayed in each of the following situations: a. The current number of jobs is 10, and the job limit is 12. b. The current number of jobs is 5, and the job limit is 10. Expressions. Variables in the IF-THEN-ELSE statement are used in conjunction with certain math operations. These operations are represented by symbols.
Using Variables and Expressions a. Print on the screen the current number of sessions and the session limit. b. Print the message, ***TOO MANY PEOPLE ON SYSTEM --- LOG OFF NOW*** Note Otherwise, do the following: c. Print on the screen the current number of sessions and the session limit. d. Print the message, ***CURRENT SESSION LIMIT NOT EXCEEDED*** . Hints are on this page if you need them. Try not to use the hints until you absolutely have to.
Using Variables and Expressions The user sees this: DO YOU WISH TO LIST ANY FILE(S)? (Y OR N): If the PROMPT option were not speci ed, the user would only see a blank line and have to guess what to input. It makes more sense to prompt for input in an intelligent manner, by printing some type of message. INPUT treats all user responses as string values (series of alphanumeric characters). This means that if the user enters a digit, it will be considered a string value, not a numeric value.
Using Variables and Expressions Figure 7-3. WHILE Loop WHILE condition is true DO this action ENDWHILE As long as the condition is true, the action continues. As soon as the condition is no longer true, the action stops. Note the following about the WHILE-ENDWHILE syntax: The WHILE statement must always be matched by an ENDWHILE statement. The action associated with WHILE is indented for improved readability. The keyword DO is optional.
Using Variables and Expressions Q6-11 According to the LF command le, you are initially asked a question. Until you give a certain response, the system continues to prompt you for le names. What causes this to occur? Q6-12 According to the LF command le, once you are prompted for a le name, what response can you give to terminate further prompting? Exercise 6-3: while loop 1. Write a command le called CF that does the following: a. Asks if you would like to change your prompt. b.
Using Variables and Expressions Lesson summary 7-20 1. Explicit dereferencing (with an exclamation point) should be used to display or assign variable values in any command other than SETVAR, IF, WHILE, and CALC. 2. Implicit dereferencing (no exclamation point) should be used with SETVAR, IF-THEN-ELSE-ENDIF , WHILE-ENDWHILE and CALC. 3. DELETEVAR should be used to delete user-de ned variables (both the name and the value).
8 Solutions Solutions to Module 1: Account Management Check Your Answers Is Your Answer . . . ? 1. AM=Account Manager AL=Account Librarian GL=Group Librarian ND=*Nonshareable Devices SF=*Save File BA=*Batch Access IA=*Interactive Access PH=Process Handling If Not, Start With Lesson 1 * indicates default capability 2. 3. 4. 5. 6. 7. 8. 9. Indicate account manager, general user, or system manager: 1. List information on their account (AM, GU, SM) 2. Change their account capabilities (SM) 3.
Using Variables and Expressions Lesson 1 Managing Your Account Q 1-1 AM AL GL ND Code SF BA IA PH Q 1-2 Q 1-3 Q 1-4 Capability Account manager Account librarian Group librarian Nonshareable devices (such as a tape drive or hot printer) Save les Batch access (for running jobs) Interactive access Process handling (needed for programming functions) No. Since PM is not one of your account's capabilities, no user may have this capability. Access is restricted to member of this account. e. all of the above.
Using Variables and Expressions Lesson 2 Managing Groups Q 1-5 a. b. c. Q 1-6 Q 1-7 PH IA BA PM MR DS Code Most CPU time: PUB Group Most le space: CLASS Group Least connect time: PROJECT Group A user having account manager capability is able to list information for all groups within an account. Users without account manager capability may only list information for their current group.
Using Variables and Expressions *********** End of Exercise 1-2 ************ Exercise 1-3: Using ALTGROUP 1a. 1b. 1c. ALTGROUP PROJECT;PASS=PJ ALTGROUP GO;CAP= ALTGROUP SLOW;ACCESS=(R,W,A,X:GU) This results in no user having Lock or Save access to the group. More speci cally, account users (except AM) cannot create permanent les without Save access to the group. 1d. ALTGROUP SLOW;PASS= 3. LISTGROUP or LISTGROUP groupname ************* End of Exercise 1-3 ************ Exercise 1-4: Using ALTSEC 1.
Using Variables and Expressions Lesson 3 Managing Users Q 1-9 LISTUSER displays information about one or more users in an account or on a system. Exercise 1-5: Using LISTUSER 1. 2. 3a. 3b. These LISTUSER parameters are optional: The name(s) of the user(s) and account(s), the output le name, and the keyword, PASS. The parameters default to these values: The name of the user and account will be all of the users in your logon account. PASS will be ignored, and no password will be displayed.
Using Variables and Expressions Q 1-12 Q 1-13 To list all the users on the system, you must have SM capabilities. If you have neither AM nor SM capabilities, you can list the capabilities of your current user. To change MYUSER's password to MYPASS, you would use this command: ALTUSER MYUSER.ACCTx; PASS=MYPASS Q 1-14 a. After you make this change, MYUSER remains logged on; however, when MYUSER logs o and tries to log on again, he or she must specify the new password. b. You must have AM capabilities.
Using Variables and Expressions Solutions to Module 2: File Management Check Your Answers Is Your Answer . . . ? 1. 2. 3. 4. 6. Lesson 1 Introduction to Files a. LISTFILE,2 b. LISTFILE,3 c. LISTFILE, -1 d. LISTFILE,1 e. LISTFILE,6 a. permanent le b. temporary le c. formal le designator Lesson 1 BUILD FILE1;REC=-80,,F,ASCII Lesson 2 Lesson 3 Lesson 1 a. keyboard b. terminal screen c. \bit bucket" d. created during the compiling of a program e. created when compiling is complete 1. LISTEQ 2.
Using Variables and Expressions Exercise 2-1: Lesson 2 Review 1. a. b. c. d. e. f. g. File Characteristics Permanent File names are 1-8 characters long. File names are aliases for devices. File names may begin with a $. Files may be listed with LISTFILE. Files may be listed with LISTEQ. File names may begin with an alpha character. Files are listed with LISTFILE ;TEMP. X Formal Temporary X X X X X X X X X 2a. LISTFILE @.@,2 2b. LISTFILE MYJOB1,-1 2c. LISTFILE MYJOB1,1 2d. LISTFILE,3 2e.
Using Variables and Expressions b. BUILD FILE2;REC=256,,V,BINARY c. BUILD FILE3;REC=-88,,V,ASCII 2. The following is the BUILD command necessary to create a le with the following characteristics: record size = 80 bytes record length = fixed length file type = ASCII BUILD myname;REC=-80,,F,ASCII ********** End of Exercise 2-2 ********* Lesson 3 Creating Temporary Files Exercise 2-3: $OLDPASS Follow the designated steps to generate $OLDPASS and $NEWPASS: 2.
Using Variables and Expressions FILE MAILPRNT=$STDLIST To redirect HP Desk messages to the line printer, you might change the le equation as follows: FILE MAILPRNT;DEV=LP Q 2-14 According to the rst le equation, the name and characteristics of the le associated with FILEIN are the following: File name Record size Blocking factor Record type File type Q 2-15 MYFILEA 80 bytes (default) fixed length ASCII According to the second le equation, the name and characteristic of the le associated with FILEOUT a
Using Variables and Expressions 4c. FILE INPUT=MYFILE1;REC=-80,,F,ASCII 4d. FILE OUTPUT = $NULL 5a. 5b. 5c. 5d. 5e. 6a. What is the name of the le designator? INPUT What le does it refer to? MYFILE1 What happens if a program reads from *INPUT? It reads the contents of MYFILE1.
Using Variables and Expressions Solutions to Module 3: Batch Processing Check Your Answers Is Your Answer . . . ? 1. 2. 3. b,c 4. !JOB JOBx,USERx/UPASSx.& !ACCTx/APASSx;INPRI=8;OUTCLASS=LP,1 !PRINT MYFILE1;OUT=*LP !EOJ Lesson 2 5. a. b. c. STREAM JOBFILE Lesson 3 d. STREAM JOBFILE;DAY=WED;AT=22:00 8-12 Solutions SCHED, WAIT, INTRO, EXEC, SUSP a. b. c. d. jobfence session limit input priority job limit Lesson 1 Lesson 1 Lesson 1 STREAM JOBFILE;AT=23:00 STREAM JOBFILE;DAY=MON; AT=8:00 6.
Using Variables and Expressions Q 3-1 a. b. c. d. e. f. g. Q 3-2 Q 3-3 Q 3-4 Q 3-5 Q 3-6 Q 3-7 Q 3-8 Q 3-9 Q 3-10 Q 3-11 Q 3-12 Q 3-13 Characteristic interactive processing. synonymous with batch processing. does not require constant supervision. submits a single command at a time. can be scheduled to run at speci ed time. most time/resource e cient. Executes with STREAM command. Jobs Session X X X X X X X Only J32 is executing. Job J35 is being submitted. J30 is awaiting execution.
Using Variables and Expressions Exercise 3-1: Lesson 1 Review 1. TRUE 2. FALSE 3. TRUE 4. TRUE 5. FALSE ************* End of Exercise 3-1 *********** Lesson 2 Examining a Job File Q 3-14 JOB Command Parameter User Name Account Name Group Name Job Name Time INPRI RESTART OUTCLASS SPSAVE Q 3-15 Q 3-16 Required Optional X X X X X X X X X MYJOB1 is the job name; ACCTx is the account name; USERx is the user name; CLASS is the group name. No.
Using Variables and Expressions Q 3-23 The print priority of the output is 1. The line printer (LP) is scheduled to print the output; however, the output does not print until the priority, currently 1, has a value above the outfence. Exercise 3-2: Lesson 2 Review 1. !JOB MYJOB2, USERx/UPASSX.ACCTx/APASSX 2. SHOWJOB STATUS (to verify jobfence) !JOB MYJOB2...;INPRI=10 jobfence);... 3. (or 1 greater than the !JOB MYJOB2,....ACCTx/APASSX,CLASS ;INPRI=10;RESTART;.... 4. !JOB MYJOB2.....;OUTCLASS=LP,1 5.
Using Variables and Expressions Q 3-26 1. 2. 3. 4. 5. 6. 7. 8. Q 3-27 Q 3-28 You should match the descriptions and command as follows: Command STREAM JOBFILE STREAM JOBFILE ;AT=8:00 STREAM JOBFILE ;AT=20:00 STREAM JOBFILE ;IN=,+8 STREAM JOBFILE; IN=+1,+8 STREAM JOBFILE; DATE=08/09/89; AT=20:00 STREAM JOBFILE ;DAY=MONDAY ;AT=22:00 STREAM JOBFILE; DATE=08/09/89 d. c. g. f. h. b. Description Job runs immediately. Job will run today, at 8:00 A.M. Job will run today, at 8:00 P.M.
Using Variables and Expressions Lesson 4 Monitoring Job Progress Note Q 3-34 There is one le associated with JOB1: $STDLIST If you do a LISTSPF at just the right moment, a spool le called EDTLIST may appear in the display. EDTLIST is a transitory spool le associated with the editor. Q 3-35 Q 3-36 The priority of the $STDLIST spool le is 1. This should be below the outfence, which is generally 7. When the spool le is no longer active the spool le \disappears" from the LISTSPF display.
Using Variables and Expressions Solutions to Module 4: File Transfer Check Your Answers Is Your Answer . . . ? 1. FCOPY FROM=MYJOB1.PUB ;TO=MYJOB1.CLASS;NEW Lesson 1 2. FCOPY FROM=STATS.PUB.ADVUSER ;TO=STATS.CLASS;NEW Lesson 1 3. FILE FILEA;REC=-80,,F,ASCII ;ACC=APPEND ;DISC=10000 FCOPY FROM=FILE1;TO=*FILEA;NEW FCOPY FROM=FILE2;TO=*FILEA FCOPY FROM=FILE3;TO=*FILEA Lesson 1 4. FILE T;DEV=TAPE FCOPY FROM=MYJOB1;TO=*T Lesson 1 5 6. 7. STORE @.PUB.
Using Variables and Expressions ********** End of Exercise 4-2 ******* Q 4-3 FILE OUT;DEV=LP FCOPY FROM=MYJOB2.PUB.ACCTx;TO=*OUT Q 4-4 You need to add an asterisk before the T (tape le name) in the FCOPY command in order to copy the le to tape. FCOPY FROM=MYJOB1.PUB.ACCTx;TO=*T Exercise 4-3: Lesson 1 Review 1. Tasks a. Release le before copying. b. De ne the device le(s). c. Fully qualify the le names (name.group.account). d. Backreference device le names with asterisks. e.
Using Variables and Expressions b. d. c. e. a. Step Action Release the le. Log on to the destination account. Enter the FCOPY command. Use LISTFILE to check the copy transfer. Log on to the source account and secure the original le. ********** End of Exercise 4-3 *********** Lesson 2 Storing and Restoring Files from Tape Q 4-5 To store all the les in your account to tape you would enter: STORE @.@;*T Q 4-6 To store all les on a tape to be restored to an MPE V system, you would enter: STORE M@.
Using Variables and Expressions Solutions to Module 5: User Commands Check Your Answers Is Your Answer . . . ? 1. 2. 3. 4. If Not, Start With TRUE FALSE An abbreviation for User-de ned command. a. UDC executes. b. The system command executes. Lesson 1 Lesson 1 Lesson 1 Lesson 2 5. HELP UDCname 6. SETCATALOG 7. SETCATALOG UDCfile;APPEND 8. OPTION NOPROGRAM 9. OPTION RECURSION 10. a. The le MONEY prints out. b. The les DOLLARS and CENTS print out. 11.
Using Variables and Expressions Lesson 1 UDCs and Command Files Exercise 5-1: Lesson 1 Review 1. a. b. c. d. e. f. g. h. 2. 3. a. b. c. Characteristics Command Files UDC Files X X X Must be cataloged. Uses commands and parameters Command de nitions must be separated by asterisks. Can easily be converted to the other. Executes the OPTION LOGON. Can be created with a text processor. Invoked by a command header. Invoked by a le name. a. b. c. d.
Using Variables and Expressions Lesson 2 Understanding Search Priority and Search Path Q 5-1 Q 5-2 Q 5-3 a. user UDC SM b. account UDC LF c. user UDC TRYIT The UDC le executes. The UDC MYFILEX executes. Exercise 5-2: Lesson 2 Review Search path and execution priority problems include: 1. system command LISTFILE 2. program le DELFILE in your current group 3. MPE/iX command PRINT 4. command le MYLIST ************** End of Exercise 5-2 ************* Lesson 3 Cataloging UDCs Q 5-4 a.
Using Variables and Expressions SHOWOUT ST *** ********** End of Exercise 5-3 ********** Q 5-5 To make the UDC not executable from within a program, you need to add the NOPROGRAM option: LF OPTION NOPROGRAM LISTFILE *** Q 5-6 a. SHOWTIME is displayed. The LISTFILE command is not displayed because it is preceded by OPTION NOLIST. b. No MPE/iX commands are displayed because the OPTION NOLIST is still in e ect. c. No MPE/iX commands are displayed because the OPTION NOLIST is still in e ect.
Using Variables and Expressions Lesson 5 Using Parameters Exercise 5-5: Using Parameters 1. The LS command le should look like this: PARM FILE NAME,OPTION="1" LISTFILE !FILE NAME,!OPTION 2a. 2b. When you enter LS without any options, the following happens: LISTFILE,1 executes by default. When you enter LS with option 1, the following happens: LISTFILE,1 executes. When you enter LS with option 2, the following happens: LISTFILE,2 executes.
Using Variables and Expressions Solutions to Module 6: Variables and Expressions Check Your Answers If Not, Start With Is Your Answer . . . ? 1. Lesson 1 VAR_1 VARIABLE_1 2. 3. 4. 5. HPPROMPT or HPPATH Lesson 1 Lesson 1 Lesson 1 Lesson 1 FALSE TRUE SHOWVAR VARIABLE1 or ECHO !VARIABLE1 6. ECHO HELLO --- WELCOME TO THE ... Lesson 2 - OR SETVAR A "HELLO -- WELCOME TO THE ... " SHOWVAR Aor ECHO !A 7. 8. 9.
Using Variables and Expressions Lesson 1 Understanding Variables Q 6-1 The following are acceptable names for variables: Variable Name b. c. d. f.
Using Variables and Expressions HPJOBLIMIT HPJOBCOUNT Q 6-6 Q 6-7 No, neither variable is user-modi able. In the LF command le, the three user-de ned variables are: RESPONSE FILE NAME OPTION Exercise 6-1: Variables 1. To de ne a variable called MYPROMPT and assign it the value currently stored in HPPROMPT, enter the following: SETVAR MYPROMPT HPPROMPT 2. To display the value of MYPROMPT, enter the following: SHOWVAR MYPROMPT 3.
Using Variables and Expressions b. The current number of jobs is 5 and the job limit is 10. d a c b ***NUMBER OF JOBS IS STILL REASONABLE --- STREAM JOB NOW*** Exercise 6-2: IF-THEN-ELSE Statement 1.
Using Variables and Expressions d a c b SETVAR HPPROMPT,":" ************ End of Exercise 6-3 ************ 8-30 Solutions
Glossary This glossary de nes terms found in the Fundamental Skills and Advanced Skills courses. Terms that appear only in the Advanced Skills course are identi ed by the notation (AS) following the de nition. abort A procedure that terminates a program or session if an irrecoverable error, mistake, or malfunction occurs, or if the system manager requests termination. access codes Access codes are assigned by the system manager to accounts.
Using Variables and Expressions ASCII attribute backreference backup batch processing binary Boolean byte capability Glossary-2 graphics, database management, and data communication programs. American Standard Code for Information Interchange: ASCII is the standard method of representing character data (seven data bits plus one that can be used for parity).
Using Variables and Expressions Capabilities are assigned to accounts, groups, and users to provide system security and access to the operating system. Account capabilities are assigned by the system manager when the account is created. The account manager then assigns capabilities to groups and users within the account. carriage control Carriage control characters determine such characters (CCTL) things as double spacing, vertical line spacing, and page ejects.
Using Variables and Expressions con guration console continuation character cursor database default delimiter dereferencing device device le directory Glossary-4 The way in which a computer and peripheral devices are programmed to interact with each other. A terminal, usually designated logical device 20, given unique status by the operating system. The operator uses the console to monitor and manage jobs, sessions and resources, respond to requests, and communicate with other user terminals.
Using Variables and Expressions disk drive echo editor environment le error listing error message execute explicit dereferencing expression FCOPY le directory may also contain information such as le size, creation date, modi cation dates, creator, or security information. (AS) A peripheral device that reads information from and writes information to the disk. To display on the terminal screen data being typed on the keyboard.
Using Variables and Expressions le equation le name formal le designator fully quali ed le name function keys group group librarian capability hard reset Glossary-6 A method of equating a le name to a device or another le. The MPE/iX FILE command is used to establish the relationship of the le to the device. Generally used to direct the input or output of a program, job, or session to a particular device by referencing the device class, such as TAPE or LP.
Using Variables and Expressions hardware header Help facility hexadecimal history stack home group HP Desk IF-THEN-ELSE statement implicit dereferencing All the physical components of the computer including the CPU cabinet, tape drives, disk drives, terminals, and other peripherals. The rst page printed when output is directed to a line printer. It contains the session name (if designated), session number, logon identi cation, day of the week, date, and time.
Using Variables and Expressions WHILE commands. input priority integer integer value interactive job jobfence job le job limit job listing Glossary-8 See also explicit dereferencing. (AS) A number in the range of 1 (lowest priority) to 14 (highest priority) assigned to input jobs. The input priority can be assigned by the system (default is 8) or by the user. Jobs with an input priority less than or equal to the system jobfence (default 7) are deferred.
Using Variables and Expressions job number keyboard keyword K le laser printer LDEV number line editor line printer link listing local mode lockword A system assigned identi cation number given to each job when it is submitted for processing. A keyboard is attached to a terminal and used to input data to communicate with the system. A word assigned a speci c meaning by the operating system, a subsystem, computer language, or utility.
Using Variables and Expressions logical device number An LDEV number is assigned to all peripherals of a computer system and is used for identi cation purposes. log o A method of terminating a session. To log o MPE/iX enter the BYE or EXIT command. log on A method of initiating a session. To log on to MPE/iX enter the HELLO command and a valid user and account name, plus a group name if necessary, and any required passwords. log on identity A security device used to verify users to the system.
Using Variables and Expressions octal $OLDPASS online operating system optional parameter outclass priority outfence output priority overwrite paging unneeded output from an executing program. (AS) Octal is a base eight number system in which digits 0 through 7 are used. One octal digit can be represented by three binary digits. Octal numbers are preceded by a percent sign (%); for example, %775 is the same decimal 509. (AS) A system-de ned le.
Using Variables and Expressions parameter partly quali ed le name password path peripheral permanent le printer program programmer prompt PUB group PUB.SYS queue Glossary-12 A value passed to a procedure, which then uses it in calculations or to determine operations within the procedure. A designation identifying the group in which a le resides. A partly quali ed le name may be used to access a le in another group of the account to which you are logged on.
Using Variables and Expressions the next job in priority is selected and processed. quiet mode When a session is running in quiet mode, messages sent from other jobs or sessions are not displayed on the terminal screen. Warning messages from the system console override quiet mode and are displayed on the terminal screen. record A collection of data treated as a unit, residing in a le. (AS) recursion The ability of a procedure or function to call itself. redo stack See history stack.
Using Variables and Expressions session session limit session name session number soft keys soft reset software SORT-MERGE/iX source code spool le Glossary-14 into groups and users into accounts, both of which may be assigned a password. Security also refers to the ability to read, write, append, lock, save, and execute les. Assigned to accounts by the system manager and to groups and users by the account manager. An interactive way of communicating with a computer.
Using Variables and Expressions PRINT, DEFER, SPSAVE, PROBLM, DELPND, or XFER. These states describe di erent spooling standalone $STDIN $STDLIST STORE subsystem stream string value subcommand subsystem syntax SYS account stages of the spooling process depending upon whether the le is an input or an output spool le. (AS) A method of managing jobs. Multiple users can send output to a nonshareable device, such as a tape or line printer, and their output is directed to spool les on disk.
Using Variables and Expressions the les for system supported subsystems, utility programs, and compilers. system console See console. system-de ned les Files de ned by MPE/iX and made available to all users. They indicate standard input or output devices, special temporary les, and les opened for output that do not perform an actual write operation. (AS) system-de ned Command interpreter variables are used to variables store system assigned information.
Using Variables and Expressions the header printed as the rst page of a document. truncate To cut o or shorten data. If too many characters appear on a line, they may not all be recognized by the system or printed as output. user A person logged on to the computer. Each user is identi ed by a user and account name. A user logs on to a session and can access les in the logon group. user command A user command is a UDC or command le created to execute one or more MPE/iX commands.
Using Variables and Expressions Welcome message WHILE loop wildcard character word word processor Glossary-18 sessions on the system, including those running in quiet mode. A message created by the system operator that is displayed each time a user logs on to the system. It usually contains a greeting and important system information. A statement used to determine what action occurs. When the conditions are true, the action is performed repeatedly in a continuous loop.
Index A aborting a job, 4-16, 4-23 ABORTJOB, 4-23, 4-24 acceptable variable names, 7-6 access codes, 2-4 Append, 2-4 Execute, 2-4 Lock, 2-4 Read, 2-4 Write, 2-4 access control de nition (ACD), 2-11{13 access to les, 2-4 account capabilities changing, 2-4 account management, 2-2 account use, 2-8 ACD (access control de nition), 2-11{13 ACTIVE state, 4-34 adding a new group, 2-14 adding UDC les, 6-16, 6-17 alert system operators, 4-13 aliases, 3-23 alias les, 3-9 ALLOW, 4-25 ALTACCT, 2-21 altering spool le, 4
Index-2 B backreferencing le equations, 3-25 back up les, 5-11 batch le, 4-2 batch processing, 4-2, 4-7 commands, 4-9 blocking factor, 3-15 Boolean values, 7-7 BREAKJOB, 4-24 BREAK/NOBREAK UDC option, 6-18, 6-23 BUILD, 3-12, 3-13, 3-13 BUILD command options, 3-16 building disk les, 3-12 bytes in a record, 3-15 C CALC, 7-12 capabilities, 2-26 account, 2-3, 2-4 account librarian, 2-4 account manager, 2-2 default, 2-4, 2-9 group librarian, 2-4 user, 7-8 capability requirements, 2-21 cataloging UDC les, 6-
JOB, 4-10 LIMIT, 7-5 LISTACCT, 2-3, 2-4, 2-5 LISTEQ, 3-9, 3-23 LISTFILE, 3-3 LISTFILE;TEMP, 3-9, 3-19 LISTGROUP, 2-8 LISTUSER, 2-25 NEWGROUP, 2-14 NEWUSER, 2-27 PURGE, 3-9 PURGEGROUP, 2-15 PURGEUSER, 2-28 REPORT, 2-8 RESET, 3-31 RESTORE, 5-10, 5-13 RESUMEJOB, 4-24 SETCATALOG, 6-5, 6-14, 6-15 SETVAR, 7-3, 7-4, 7-8 SHOWCATALOG, 6-5, 6-14, 6-15, 6-16 SHOWJOB, 4-3 SHOWOUT, 4-11 SHOWVAR, 7-3, 7-4, 7-8, 7-9 SPOOLF, 4-33 STORE, 5-10, 5-11, 5-11 STREAM, 4-2, 4-16, 4-21, 4-21, 4-27 TELL, 4-13 TELLOP, 4-13 user, 6-3
copy les to tape, 5-10, 5-11 copying les, 5-2 between accounts, 5-4 between groups, 5-4 from disk to other devices, 5-7 to and from devices other than disk, 5-7 within an account, 5-3 copying functions, 5-2 creating accounts using MKACCT, 2-16 a directory of les on tape, 5-11 a new user, 2-27 a UDC, 6-14 command sequences, 6-3 groups using MKACCT, 2-16 spool les, 4-27 users using MKACCT, 2-16 creator listing, 3-5 customized les create, 3-12 D Index-4 default capabilities, 2-4, 2-9 density, 5-12 default p
DO, 7-18 duplicate les, 5-3 E ECHO F FCOPY, 3-13, 5-2, 5-2 commands, 7-11 EDIT/3000 commands, 4-16, 4-18, 4-20 editor comments, 4-19 empty le, 3-29 end a job, 4-18, 4-20 ENDWHILE, 7-18 EOJ, 4-13 erasing the original le from disk, 5-13 examining UDCs, 6-19 executable code, 3-19 execute a command le, 6-12 execute the UDC, 6-12 executing command sequences, 6-3 executing UDCs from a program, 6-22 explicit dereferencing, 7-11 expressions, 7-3, 7-15 le access attributes Append, 2-10 Execute, 2-10 Lock, 2-10
structure, 3-5 les alias, 3-9 alternate label, 3-9 building disk, 3-12 create customized, 3-12 device, 3-9 formal, 3-9 information on one le, 3-4 introducing, 3-3 passwords, 3-14 permanent, 3-3, 3-4 security, 2-11, 3-14 system-de ned, 3-7 temporary, 3-3, 3-7 user-de ned, 3-30 le security, 2-11 le transfer, 5-10 le type ASCII, 3-16 formal le designators, 3-3, 3-23 formal les, 3-9, 3-23 fully quali ed le names, 5-4 Index-6 G group assignments, 2-8 attributes, 2-9 passwords, 2-13 H header line, UDC, 6-14
I IF-THEN-ELSE-ENDIF J JLIMIT, 4-4 statement, 7-13 implicit dereferencing, 7-11, 7-12 increasing security, 2-26 initiate the STORE process, 5-11 input les, 3-8 priority, 4-25 priority values, 4-4 INPUT, 7-16 integer variable types hexadecimal, 7-6 octal, 7-6 interpreter command, 6-35 invalid names, variable, 7-6 invoking command les, 6-3 job batch processing, advantages, 4-2 mode, 4-2 number, 4-23 priority, 4-4 JOB, 4-10 account name, 4-10 logon group name, 4-10 passwords, 4-10 user name, 4-10 JOB comma
L LF command LIMIT, 7-5 les, 7-3 limit, job, 7-3 linker, 3-19 list information on a particular job, 4-6 information on current jobs, 4-6 jobs scheduled, 4-6 job summary information, 4-6 status of all jobs, 4-6 LISTACCT, 2-3, 2-4, 2-21 LISTACCT command PASS parameter, 2-5 LISTEQ, 3-9, 3-23 LISTFILE command options, 3-4 parameters, 3-3 LISTFILE;TEMP, 3-9, 3-19 LISTGROUP, 2-8 list group passwords, 2-13 listing account information, 2-3 creator, 3-5 le equations, 3-9 groups, 2-8 lockword, 3-5 security informa
mounting tapes, 5-11 N name duplication, 6-12 names invalid, 7-6 valid, 7-6 variable, 7-5 negative record size, 3-15 NEWGROUP, 2-14 NEW option of FCOPY, 5-3 $NEWPASS le, 3-8, 3-18, 3-18, 3-19, 3-28 NEWUSER, 2-27 $NULL le, 3-18, 3-21, 3-28 O object code, 3-19 octal integers, 7-6 $OLDPASS, 3-18 $OLDPASS le, 3-8, 3-18, 3-19, 3-28 online help facility, 2-23 operations arithmetic, 7-15 mathematical, 7-15 relational, 7-15 optional parameters, 2-24 OPTION LOGON, 6-6 options position of, 6-24 TRANSPORT, 5-12 op
Index-10 P parameters bene ts of, 6-33 multiple, 6-30 optional, 2-24, 6-27, 6-29 required, 6-27, 6-29 STORE, 5-13 TRANSPORT, 5-12 using, 6-27 passwords, 4-10 group, 2-13 listing account, 2-5 logon, 2-5 user, 2-5, 2-26 password security, 2-5 permanent les, 3-4 position of options, 6-24 prede ned variable names, 7-7 priority for jobs, 4-4 high, 4-4 input, 4-11, 4-25 low, 4-4 output, 4-25 processing and printing priorities input and output, 4-8 PROGRAM/NOPROGRAM UDC option, 6-18, 6-22 prompt MPE XL, changing
RESUMEJOB, 4-24 resuming a job, 4-16, 4-24 reversing the STORE procedure, 5-13 S sample worksheet account structure, 2-16 search directory, 6-9 path, 6-9, 6-12 priority, 6-9 searching command directories, 6-11 le directories, 6-11 UDC directories, 6-10 search priority, 6-9 security le, 3-14 les, 2-11 password, 2-5 security information, listing, 2-3 send a message, 4-13 session mode, 4-2 sessions comparison, 4-3 logged on, 4-4 SETCATALOG, 6-5, 6-14, 6-15 SETCATALOG command APPEND option, 6-16 DELETE optio
specify an input priority, 4-20 spooler commands, 4-27 SPOOLF command, 4-33 SPOOLF command DELETE, 4-34 spool le, 4-27 altering, 4-33 purge, 4-34 spool le information displaying, 4-27 standard input device, 3-29 standard output device, 3-29 STATS command le, 7-3, 7-11 $STDIN le, 3-7, 3-28 $STDLIST le, 3-7, 3-28 stopping UDC execution, 6-23 STORE, 5-11 STORE command using, 5-11 STORE parameters, 5-13 PROGRESS, 5-13 PURGE, 5-13 SHOW, 5-13 storing les on tape, 5-10 system information, 7-7 user information,
T tape labels, 5-12 TELL, 4-13 TELLOP, 4-13 temporary les, 3-7 concepts, 3-18 creating system de ned, 3-18 displaying names, 3-18 listing, 3-9 $NEWPASS, 3-8, 3-18, 3-18, 3-19 $NULL, 3-18 $OLDPASS, 3-8, 3-18, 3-18, 3-19 purging, 3-9 $STDIN, 3-7 $STDLIST, 3-7 using to redirect output, 3-18 terminate a job, 4-13 toggling between an editor and the OS, 6-35 transferring les, 5-10, 5-12 between locations, 5-11 transporting les to a new system, 5-12 TRANSPORT option to STORE, 5-12 troubleshooting MKACCT, 2-21 typ
RECURSION/NORECURSION , 6-18 uncataloging UDC les, 6-14, 6-15 user changing password, 2-5, 2-26 password, 2-5, 2-26 user capabilities, 2-26 user commands, 6-3 user-de ned commands, 6-3 user-de ned les, 3-30 user-de ned variables, 7-7, 7-9 user les, 3-4 user-related tasks, 2-23 using MKACCT command le, 2-16 using variables, 7-11 utilities FCOPY, 5-2 RESTORE, 5-10 STORE, 5-10, 5-11 V Index-14 valid names, variables, 7-5 variables, 7-3 assigning, 7-4 Boolean, 7-7 creating, 7-4 de ning, 7-4 dereferencing, 7-
W WHILE, 7-17, 7-18, 7-19 X XEQ, 6-9, 6-12 words, two-byte, 3-15 worksheet sample for account structure, 2-16 Index-15
