Introduction to the WYLBUR Text Editor.
Chapter 1: Getting Started.

Commands. Index. Glossary.

On this page:


line.


Some Basic Things to Know

As an account holder, you can access the IBM mainframe using your userid and password. This is called logging on to the computer and will be discussed shortly. Once logged on, you will be able to invoke WYLBUR. The WYLBUR text editor uses English-like commands, and most of those commands may be abbreviated to the first three--or more--characters (e.g., SHO TIM can be typed instead of SHOW TIME).

Entering Commands

When you see COMMAND? on your screen, WYLBUR is requesting that a command be typed. WYLBUR commands can be given only from this prompt, the abbreviated "?" that you can get by typing the SET TERSE command (SET VERBOSE is the command that returns the system to the default COMMAND? mode), or the ">" (if you have placed your session in upper/lowercase mode with the command SET UPLOW). In this manual, the COMMAND? prompt will be used in all the WYLBUR examples.

To give WYLBUR a command, type the command word or phrase and press ENTER. Pressing the ENTER key (not the RETURN key) tells WYLBUR that you are finished typing the command. If you make a mistake, WYLBUR will not understand the command and will give you an error message or prompt you for the necessary information. Simply type the command again at the COMMAND? prompt and press ENTER.

Command Conventions

As previously mentioned, commands and their parameters may be abbreviated to the first three or more characters. Characters that are recognized as separators of command parameters are the blank ( ), comma (,), and equal sign (=). A forward slash (/)[1] designates a range of lines (e.g., UPDATE 7/15 will display lines 7 through 15 of your file for updating). A semicolon (;) designates the end of a command on a line. Anything following the semicolon will be considered by WYLBUR to be a comment and will not be read as part of the command. You will find that using comments to explain your actions for using a particular command is not only a useful reminder but an aid to anyone who is allowed to read and/or use your file (security information regarding your files in WYLBUR).

Correcting Typing Mistakes

Typing errors are inevitable for everyone when typing either commands or text. There are ways, however, to correct your text using different keys on the keyboard.

Keys for Corrrecting Typing Errors
Key Function in WYLBUR
BACKSPACE Each time you press this key (usually located in the same position as on a typewriter keyboard), the character to the immediate left of the cursor will be deleted.
BACKTAB If you have typed a command totally wrong, rather than pressing ENTER and having WYLBUR tell you it is incorrect, press the BACKTAB key (this will be labeled differently on various terminals). This will place you back at the beginning of the line, and you can type the command again.
ARROW There are four arrow keys on the right-hand side of your keyboard, which move the cursor up, down, right, and left, respectively. If you type only part of the command wrong and do not want to type the whole command over, use the BACKSPACE key or the left arrow key to move the cursor back to the mistake and type over it with the correct characters. If you are entering text and notice that you have made a mistake in a previous line, you can use the up arrow key to move the cursor up to the mistake and correct it. Then use the other arrow keys to move back to where you had been typing. When you move the cursor over text with the arrow keys, the text you pass over is not affected.
EOF If you make a mistake that is longer than the correction, you can use this key. It erases from the cursor to the end of the line. Use the arrow keys to move to the mistake, correct it, press EOF (which will erase the remainder of the command on the line), and then press ENTER.
INSERT Sometimes you will make a mistake in which you will need to add or delete a few characters from what you have typed. Use this key to add characters. With the arrow keys, move the cursor to the character to the right of where you want to add something. Press the INSERT key (this will be labeled differently on various terminals) and type in the characters you need. Press ENTER.
DELETE Use this key to delete characters. With the arrow keys, move the cursor to the left-most character you want deleted. Press the DELETE key (often labeled DEL; do not confuse it with the BACKSPACE key). The character at the cursor will be deleted, and the character to the right of the cursor will move to the left under the cursor. Keep pressing DELETE until all of the extra characters are gone. Press ENTER to send your corrected command to WYLBUR.

Logging On

Before you sit down at your terminal, make sure you know your TechNet userid and password. You will log-on to WYLBUR through the TechNet Screen displayed below.

TECHNET screen.

The cursor will be blinking beside Userid. Type in your userid to begin identifying of yourself to the computer as a legitimate account holder. Press the NEWLINE key, and the cursor will jump to Password. Type your password (because this must remain your secret, it will not show on the screen as you type it). Press NEWLINE. If you have typed both correctly, you will have proved you are the owner of a TechNet account. The cursor will now be beside System. Type wylbur and press ENTER . This will tell the computer you wish to use WYLBUR, and the TechNet screen will disappear. If it does not, and

INVALID USERID or WRONG PASSWORD

appears in the lower, left-hand corner of the screen, press NEWLINE until the cursor is beside Userid again and start over. If you see any other message, refer to System Messages for more information.

A Little More on Passwords

Only you should know your password because anyone else who knows it can use your TechNet account. You are responsible for your own account and its files. Do not give your password to others. To help you remember to change your password often, the computer will make you change it with the SETPASS screen. Passwords are from three to eight characters long. The very first time you log-on to the computer, you will get the SETPASS screen (shown below). If you have already logged on and changed your password, you will not get this screen again until the system requests a change. The system remembers the last four passwords you have used and will not allow you to reuse them until you have used a fifth. You may, if you wish, rotate these five (starting back with 1, then 2, etc.).

The SETPASS Screen

=======================SETPASS=======================
Press any PF key to exit without changing password
Your password expires every 006 days

Password:    Type in your new password.
             Press tab key and type it again.

Password:    Type in exactly the same both times.
             Press the ENTER key when done.

  1. Type your new password.

  2. Press NEWLINE (instead of the TAB key mentioned in the SETPASS screen).
  3. Type your password again to confirm its spelling to the computer.
  4. Press ENTER, and the new password will be added to the structure of your account.

Choosing a Password

Do not use obvious passwords, and do not write them down. Devise a method of creating unique passwords. Suggestions for selection:

  1. Do not use words found in English dictionaries.

  2. Use two words strung together.

  3. Use words or alpha-characters with numbers embedded.

  4. Develop a system that will help you remember your password but one that even those closest to you would find difficult to guess.

  5. Vary your system often.

  6. Never make your password the same as your username.

REMEMBER: Users who know your password can use your account and all the privileges with it. Use caution and protect your files (information on security of individual files).

Starting WYLBUR

Now that you are logged on, you will see messages about the IBM system itself. If MORE... displays in the lower, right corner of your screen, press ENTER.

Your cursor will be to the right of the COMMAND? prompt. At this point you can give WYLBUR instructions to begin. Here are some of the commands that can be used as you start (more information on commands).

Commands for Starting WYLBUR
Command Description
SET VOLUME volume Tells WYLBUR that, during your session, you want to save your files on the specified disk pack (volume), such as TPPAK1.
SET BIN nnn Tells WYLBUR the bin number where you want your printouts placed.
SET WINDOW lnc/nolnc This command has two choices, LNC and NOLNC (also see below).
SET DESTINATION place Tells WYLBUR where you want your printouts (e.g., Technology Support for the Advanced Technology Learning Center dispatch area).

Datasets

A WYLBUR file is called a dataset and is a collection of lines (0-232 characters each). Each line is given a unique number from 0 to 99999.999, and lines are arranged in descending order. A file can be a program file (Pascal, FORTRAN, PL/I, etc.), a section of text material, a series of WYLBUR commands, and so forth. There are four categories of files.

Dataset Categories
Category Description
ACTIVE This file is held in the computer's memory for editing purposes. The maximum size is 15 to 20 thousand lines of text.
EXTERNAL This is a file that is stored on a disk. To modify an external file, it must be made into an active file. It is identified by a dataset name (dsname), which follows specific conventions.
EXECUTE This file is distinct and separate from an active file. It is a list of commands that is activated with the EXECUTE command. The file may contain 600-800 commands.
QWIK These are files that can be taken in and out of the active file area easily and allow the user to have several files loaded into memory and ready for access.

The OBS WYLBUR Reference Manual has more detailed information on each of these file types.

Naming a Dataset

Files are identified by their dsname. Each has the format listed below. This form is called a fully qualified dsname:

[xxx.][userid.|PUB.][name|LIB][(member-name)]

Dsname Format
File Part Description
xxx an installation option of 1 to 8 characters (designated by System Management)
userid your five-character userid
PUB datasets in the space pool of the group specified by your userid
name the name you give your file to identify it from others. It may be 3 to 8 characters long with the first being an alpha character.
LIB the standard WYLBUR library name. You should have no more than one library called LIB. LIB is assumed to be the default for operations, but it is not automatically created for the new user.
member-name the name of a member of LIB. The same rules for name apply here.

All parts are not necessary to call up a file. The user may supply only a portion of the name, and WYLBUR will use system defaults to supply the remainder of the name. For example:

WYL.USERID.LIB

Entering Text in WYLBUR

To enter text, you must ask WYLBUR to collect your text into an active file. The COLLECT command is similar to putting a piece of paper into a typewriter. The active file holds the text you type just as the paper would.

Type COLLECT at the COMMAND? prompt. You will see an empty screen with a numbered grid at the top. This is where you start entering your first line. The following example is a Pascal program and can be used as practice in using WYLBUR. The NEWLINE key (not ENTER) should be pressed at the end of each line (WYLBUR will not automatically wrap lines). Use the SPACEBAR for spaces (not the arrow keys). If ENTER is pressed by mistake before the file is complete, type COLLECT again from the COMMAND? prompt.

After you have finished typing the file, check for typing errors, then press ENTER. The cursor will return to the COMMAND? prompt.

----+----1----+----2----+----3----+----4----+----5----+----6----+
****  *************************TOP OF DATA **********************
00001 //  JOB
00002 //  EXEC PASCG
00003 //PASC.SYSIN DD *
00004   PROGRAM NAMEPRINT(INPUT,OUTPUT);
00005   VAR
00006      MYNAME: PACKED ARRAY (.1..20.) OF CHAR;
00007   BEGIN (* NAME *)
00008      READLN (MYNAME);
00009      WRITELN('  MY NAME IS ', MYNAME:20);
00010   END.  (* NAME *)
00011 //GO.SYSIN DD *
00012 HEATHER
00013 //
****  *************************END OF DATA **********************

Saving Your Work

You must store your work before you log-off, or WYLBUR will erase what you have done. Save your work as a file (dataset) with the SAVE command, giving it a name of 3 to 8 characters long with no spaces and starting with an alpha character (underscores can be substituted for spaces). For example:

COMMAND? SAVE MYFILE

A message will display, similar to the following (varying according to the SET parameters specified at log-in):

MYFILE SAVED AND CATLG'D ON TPPAK1

This means that the file MYFILE was saved on the TTPAK1 volume. Next, type:

COMMAND? SHOW CATALOG

The response will resemble:

WYL.GG.UUU
MYFILE - ON TPPAK1

where GGUUU is your userid. This shows that your file has been stored under your userid on volume TTPAK1.

Running Your Job

After a program has been typed and stored, it can be sent to be processed. This is called "running a job." The following is a list of commands used to run a job. The screen responses included will differ in content according to your own submissions. First, type:

COMMAND? RUN FETCH

RUN tells WYLBUR to run a job. FETCH means you do not want the job to print until you tell it to do so. If you do not RUN FETCH, your job will print automatically. WYLBUR will ask for your password. Replace PASSWORD with the password you set with the SETPASS screen. You will then see a message similar to:

JOB 0000 UUUGG001 SUBMITTED

where 0000 is a number the computer system gives your job (remember this number; other WYLBUR commands use this number), UUUGG is your userid with the group code at the end instead of the front, and 001 means that this is the first job you have run on this account.

Whenever you see MESSAGE WAITING in the lower, left corner of the screen, press ENTER to see the message. When your job has completed, you will see (same variables as above apply):

FROM OPERS JOB 0000 UUUGG001 ENDED

Wait for this message before you go on to the next step. Type:

COMMAND? LOCATE

This asks WYLBUR to locate any jobs you have in the system. WYLBUR will respond with:

JOB 0000UUUGG001 AW FET

This means your job has run and is waiting in the system for you to FETCH it.

Reviewing Your Work

After your job has run, you can FETCH it and look it over. Use the FETCH and REVIEW commands for this. Note the following example.

COMMAND? FETCH nnnn CLEAR

where nnnn is the number the system gave your job. The job is now in the active file. The CLEAR command will erase what was in the active file before you issued the command. If you do not save a currently active file before issuing this command, then your work on that file will be lost. Type:

COMMAND? REVIEW

This tells WYLBUR you want to review or look at the job you just FETCHed. The file shown in the next screen example would be displayed if the sample Pascal file (previous example) had been run (edpag is the userid).

----+----1----+----2----+----3----+----4----+----5----+----6----+
****  *************************TOP OF DATA **********************
00001               J E S 2  J O B  L O G  --  S Y S T E M
00002
00003 09.38.27 JOB 2996  $ GGGUU001 STARTED - INIT 1 - CLASS A -
00004 09.38.28 JOB 2996  IEF403I PAGED221 - STARTED
00005 09.38.52 JOB 2007  OEF404I PAGED221 - ENDED
00006 09.38.53 JOB 2996  $ PAGED221 ENDED
00007 ------ JES2 JOB STATISTICS ------
00008 29 JUL 96 JOB EXECUTION DATE
00009        20 CARDS READ
00010       101 SYSOUT PRINT RECORDS
00011         0 SYSOUT PUNCH RECORDS
00012      0.48 MINUTES EXECUTION TIME
00013         1 //UUUGG0001 JOB (ED$PAG,EER5), 'EDPAG',
00014           // CLASS=A
00015           // NOTIFY-EDPAG
00016           ************************
00017           ***ROUTE  PRINT RMT10
****  *************************END OF DATA **********************

Parameters placed on the REVIEW command will let you review specific parts of a file. For example:

REVIEW 'CODE' OR 'ERROR'

would let you look only at lines with the words code or error in them.

To remove the job from the system, use the PURGE command:

PURGE nnnn

where nnnn is the job number assigned to your job by the system.

Editing Your File

Use the UPDATE command to correct any errors and make additions to a file. When you edit a file, you can change characters within the text the same way you do with the COLLECT command. You can also change the arrangement of lines in the file with line number command (LNC) typed over the line number fields to the left of the lines you wish to edit.

Editing Commands
Command Description
SET WINDOW lnc Tells WYLBUR you want to use line number commands (NOLNC turns this function off again). After using this command, you can type over the numbers in the line number fields.
USE dsname CLEAR Erases your active file and replaces it with the file you specify in this command.
UPDATE Lets WYLBUR know you want to edit your file. After issuing this command, you can change material in the file by typing over it or using the INSERT and DELETE keys. The arrow keys can be used to move the cursor over text you do not want to change.

You can also change your text using line number commands. Study the next two examples. Note the alpha additions to the line numbers in the first figure and the resulting changes in the second. The DD in the first example marks the first and last lines of the section that were deleted from the second example (lines 00008 through 00011). The M in line 00013 is an instruction to move that line down to the line marked with an A (00015).

----+----1----+----2----+----3----+----4----+----5----+----6----+
****  *************************TOP OF DATA **********************
00001 //  JOB
00002 //  EXEC PASCG
00003 //PASC.SYSIN DD *
00004   PROGRAM NAMEPRINT(INPUT,OUTPUT);
00005   VAR
00006      MYNAME: PACKED ARRAY (.1..20.) OF CHAR;
00007   BEGIN (* NAME *)
00008   PROGRAM NAMEPRINT(INPUT,OUTPUT);
00009   VAR
00010      MYNAME: PACKED ARRAY (.1..20.) OF CHAR;
00011   BEGIN (* NAME *)
00012      READLIN (MYNAME);
00013 //GO.SYSIN DD *
00014      WRITELIN(' MY NAME IS ', MYNAME:20);
00015   END.  (* NAME *)
00016 //
****  *************************END OF DATA **********************

The NUMBER command COMMAND? prompt renumbers the file, as shown in the second example. (If you have actually done the examples, then your name would display in place of "Heather.")

----+----1----+----2----+----3----+----4----+----5----+----6----+
****  *************************TOP OF DATA **********************
00001 //  JOB
00002 //  EXEC PASCG
00003 //PASC.SYSIN DD *
00004   PROGRAM NAMEPRINT(INPUT,OUTPUT);
00005   VAR
00006      MYNAME: PACKED ARRAY (.1..20.) OF CHAR;
00007   BEGIN (* NAME *)
DD008   PROGRAM NAMEPRINT(INPUT,OUTPUT);
00009   VAR
00010      MYNAME: PACKED ARRAY (.1..20.) OF CHAR;
DD011  BEGIN (* NAME *)
00012      READLN (MYNAME);
M0013 //GO.SYSIN DD *
00014      WRITELN('  MY NAME IS ', MYNAME:20);
A0015   END.  (* NAME *)
00016 //
****  *************************END OF DATA **********************

Lines may also be inserted with the I instruction typed on a line number. For example, to insert a line between 00015 and 00016 in the first example, type I0015.5 and press ENTER. Type text on the blank line WYLBUR gives you and press ENTER again. WYLBUR will give you another blank line on which to type. Type more text or press ENTER to tell WYLBUR you do not wish any more text inserted. When all inserts have been completed, type the NUMBER command to renumber your file.

Split Screen

The SET WINDOW command will allow you to place two separate files or different sections of the same file on the screen at the same time for editing or review. All WYLBUR commands function in either window. See the OBS WYLBUR Reference Manual for a complete description of commands used to manipulate windows.

Replacing the Original File

After the file has been updated, the new version will need to be saved and the job run again. You will want to replace the old version with the new one.

Commands for Replacing Files
Command Description
SAVE dsname REPLACE Tells WYLBUR to replace the original copy of your edited file with your new version (in the active file).
RUN FETCH Reruns the new version. Wait for the JOB nnnn UUUGGnnn ENDED message to appear before entering the next command (where nnnn is the job number and UUUGG is the userid, and the nnn after the userid refers to the sequence number of jobs run--e.g., 002 would mean the second job run). The LOCATE command can be used again if you wish to see what your job is doing.
FETCH * CLEAR FETCHes the last job run (using the asterisk tells WYLBUR to look for the last file used).
REVIEW 'ERROR' OR 'CODE' Locates lines that contain errors.

Printing Your Job

When your program runs with no errors, you are ready for a printout. The PRINT command used with the job number will print the job, and it will be dispatched to the location and in the bin you specified at log-in with the SET BIN and SET DESTINATION commands.

PRINT nnnn

Logging Off

When you have completed your session, you will need to log-off the computer. Type:

LOGOFF CLEAR

This commands tells WYLBUR you want to log-off the computer and erase whatever you had in your active file. Always make sure you have saved your work before you log-off.

WYLBUR will give you some information about your session, such as the time you logged on, how long you were logged on, and information about the work you did. After a few seconds, the TechNet screen will reappear. At this point your session is over.


[1]Take care not to confuse this with the backslash (\). [Return to place in text.]

line.

Site Search Options

[© 2/2001 Documentation Home] [Laws and Policies] [TTU Home Page]
Updated July 29, 2003