What is an AS400? The AS/400 (Application System/400) was first introduced by IBM on June 20th, 19 88.

The AS/400 is a popular family of mid-sized computer systems which can also be used as multiuser computer systems. By this, we mean that a single computer c an interact with more than one user at a time. The AS/400 can be utilized for different business facets. Some models are design ed as systems that provide resources to other computers, also known as a "server " in a network of computers, while others are set up for use with terminals or " display stations". OS400 is the operating system for the AS/400. The AS/400 comp uters offer more compatibility across the product line than the earlier System/3 X computers. Hence, the earlier IBM models of the System/36 and System/38 have s ince been replaced by the AS/400 systems. IBM has sold over 600,000 AS/400's and over 350,000 of them are still active. Fr om distribution warehouses to hospital administrators, and even manufacturing co mpanies, the AS/400 is a strong component in aiding these companies daily busine ss operations. The AS/400 utilizes a green screen interface, a built in database that resembles DB2, and a vast array of software to provide business solutions for todays business needs. In October of 2000, IBM rebranded the AS/400 and announced its name as the IBM i Series 400. In doing this, IBM has shown that it is evolving this mid range fami ly of computers in an attempt to keep in tune with the fast paced demands and ch anges that the Internet and the e-business world reside in. For the purposes of our tutorial, we will continue to use the term AS400 rather than iSeries, althou gh there is no distinction between the two. As well, since 95% of AS/400's use R PG, we will emphasize using RPG in this tutorial. To answer the question of "why should you bother to learn to use the AS400", che ck out some of the job sites on the web, such as computerjobs.com or monster.com , and do a search on AS400 RPG, and see the career possibilities that await you. ---------------------------------------------------------------------Showcase Article - AS/400 Commands You can run commands directly from any command line. Once you learn the commands , you can write "Control Language" or CL programs. CL programs are simply string s of commands that have been entered and compiled. So as you learn these command s, you are also learning to write CL programs. Managers and administrators who h ave duties in different environments may have trouble shifting gears from one op erating system to another. We're going to look at some easy ways to help you lea rn and remember these commands. The AS/400 operating system is consistent in its presentation and names. Command s have names of up to 10 letters. The commands typically take the form of three letters. For example, to work with active jobs, the command is WRKACTJOB. That's a single word with no spaces. WRK is the AS/400 abbreviation for "work" and ACT is the abbreviation for "active." Because the AS/400 is consistent in its namin g style, after you know some of the abbreviations, you will be able to guess the names of commands. In the sidebar are 11 important verbs and nouns that combine to form command nam es. The abbreviations are not all three letters but they are used consistently t hroughout the system. "F" is always the abbreviation for file. You won't have to guess if it is sometimes abbreviated as "FIL." If you don't know the exact name of a command, you can use the AS/400 menus to b rowse. If you key in GO VERB from a command line and hit Enter, you will go to t he AS/400 menu named VERB. This menu lists all AS/400 verbs. From here you can n

avigate and browse to the exact command you need. Also, to see the major command groups, GO MAJOR. If you already know the verb, but need the rest of the syntax, there is a menu n amed after the verb. For example, there is a CMDWRK menu with all "work" command s, there is a CMDDSP menu with all "display" commands and there is a CMDADD menu with all "add" commands. So you can key in GO CMDSTR and see all "start" comman ds. To learn more about any command, type in the number of the command and then hit F1. The AS/400 has extensive, friendly help built into every command. Some innocuous looking commands such as CPYF are deceptively powerful and comple x. CPYF can copy a file, renaming it while selecting only records in which the f ield "STATE" has a value of "DC." In fact, there are six screens of key words yo u can use. Learning this one command can give the power to clean up a master fil e by copying only records you wish to keep while bypassing data created by an er rant task. To see a comprehensive list of AS/400 Commands, click here. -sidebarIt is important to become familiar with basic AS/400 command abbreviations. The following is a list of the most commonly used verbs and nouns that combine to ma ke commands. Command Abbreviations--Verbs ADD CFG CHG CPY CRT DLT DSP GO RMV STR WRK Add Configure Change Copy Create Delete Display Go to a Menu Remove Start Work with

Command Abbreviations--Nouns DEV Device DEVD Device Description F Files FLR Folder LIB Library OUTQ Output Queue MSG Message SPLF Spool File WTR Writer (Printer) ---------------------------------------------------------------Library Lists The library list on the AS/400 is similar to the "path" on PC's. Mainframe progr ammers may compare it to the "steplib" or "joblib". It defines the order of libr aries that the operating system uses to find objects. When you execute a command or call a program, the AS/400 must know where to find the command or program. Sometimes, you specify the library explicitly. But if y ou don't, the AS/400 will find your command or program by looking in each librar

y in your library list. It will use the first one that it finds first. This is very handy for testing. If you are testing an put it in a test library which is at the top of ever you specify a program or refer to a file, the can find in the test library. If it can't find it hrough your library list until it finds it. So, setting up a test environment is as simple as: 1) Create a test library. 2) Put objects that you want to test in the library. These can be files, menus, programs or any AS/400 object. 3) Insert the test library name into your library list, before your production l ibraries. Now you can execute test programs and modify test data. The best part is that yo u don't need to copy production programs or files into the test library unless t hey will be affected by the test. That is, all those supporting database files t hat you need to run a program, but that are used for input only, do not need to be copied to the test library. Of course, if you are unsure if a file will be mo dified during your test procedure, copy it to the test library anyway. Once you have inserted the test library name in your library list, you will want to make sure everything is in the proper order. Use the DSPLIBL command to see your library list. You will probably see three types of list entries: 1) The SYS libraries have operating system objects. This is where the AS/400 com mands and menus are contained. 2) The CUR library is your current library. This is your first user library and is where objects are created if you don't specify which library to use. 3) The USR libraries list your other user libraries. Use EDTLIBL to change your USR libraries. You can rearrange the list, remove lib raries or add libraries. Notice that you can't see the SYS or CUR libraries when you use EDTLIBL. The only way to change the current library is with the CHGCURL IB command. The WRKOBJ command will help see which object is being used. This command is sim ilar to the directory ("dir") command on PC's. Use it to list objects in your li brary list. So, if you have three copies of program, "PAYCALC", in different libraries, use the command WRKOBJ PAYCALC to see which copy of "PAYCALC" will be used. The comm and will list all objects named "PAYCALC" in the sequence that the AS/400 finds them . If you ever say to yourself in frustration, "I know I changed the program but it looks like I'm still running the original program", it's a pretty good b et that you're executing a different copy of the program than you think. This is only a fraction of the power of the WRKOBJ command. It is the easiest way to na vigate through an undocumented system. When you are copying files to your test library, use special care with the logic al files. It is easy to create a logical file that resides in a test library but updates a physical file in a different library. -------------------------------------------------------------------------Review of Commands Discussed: DSPLIBL - Display complete library list EDTLIBL - Edit library list CHGCURLIB - Change Current Library WRKOBJ - Work with objects (similar to PC "dir") Example of Library List Set Up for Testing: QSYS SYS System Library QSYS2 SYS System Library for CPI's QHLPSYS SYS QUSRSYS SYS TESTFILES CUR Library for Test Files TESTPGMS USR Library for Test Programs a version of a program, you c your library list. Then, when system will use any object it there, it will look further t

GLFILES USR Library for Production G/L Files GLPGMS USR Library for Production G/L Programs PRPGMS USR Library for Production P/R Programs PRFILES USR Library for Production P/R Files TAATOOL USR Library for User Tools QGPL USR General Purpose Library QTEMP USR --------------------------------------------------------------------