1 / 27

iSeries

Learn about wildcards, library lists, CL commands, and creating CL programs on IBM AS/400. Understand how iSeries finds objects and sequencing in library lists. Enhance your knowledge with practical steps in CL programming.

christeen
Download Presentation

iSeries

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. iSeries Lecture 4

  2. ‘*’ (Asterix) • When used before an ‘AS/400’ word, indicates that the word is a special value.eg. CRTLIB LIB(MYLIB) TYPE(*TEST) TEXT(‘Test Library) • When used at the end of a word, indicates a generic combination of alphanumerics (wildcards).eg. WRKLIB TST*

  3. How does the AS/400 find Objects?

  4. iSeries finds Objects • Qualified Names Library/Object BTO230LIB/PGM1 • Using Library Lists! How are Library Lists sequenced?

  5. When would you use a Qualified Name to find an object? • The object exists in two or more libraries on your library list. • The object does not exist on your library list. • You do not have authority to the object, but want to check if it exists.

  6. iSeries finds Objects Note: Library Descriptions, Device Descriptions and User Profiles are stored in QSYS. All other Object Types can be stored anywhere.

  7. Library List • Determine where a Job finds Objects

  8. Library Lists • Each job has an attached Library List • Different Types of Libraries: • System: IBM Supplied • Product: Added automatically when an IBM product is used • Current: Defined by an individual user ID User ID’s default Library • User: Non-IBM Supplied Libraries Created by Business to organize programs, files, etc.

  9. CL Syntax Command-name (space) parameter

  10. CL • Control Language (CL) is a set of commands that you use to control operations and to request system-related functions on the IBM AS/400 computer.

  11. Naming of Commands • Based on English! • Combination of Verb and Noun CRTLIB Library Create

  12. CL Commands • Some typical nouns CL Noun English Description LIB Library Object that holds Objects LIBL Library List List of Libraries for a Job OUTQ Output Queue Object that stores Spool Files JOBQ Job Queue Object that stores Batch Jobs to be processed FD File Desc Description of file F File Object that stores data USRPRF User Profile Object that lists attributes about a Sign On Id

  13. CL • CL serves purposes comparable to Job Control Language (JCL) on mainframe computers. • CL provides much more functionality than JCL. • CL is similar to the PC-DOS commands you may use on a PC. DOS operations like copying files, redirecting output, and making directories have direct CL counterparts. • CL is very rich in function but it is not considered to be a high-level language (HLL). You would not, for example, write a payroll application using CL.

  14. CL • CL commands may be entered into the system interactively on an AS/400 command line or included in a CL program • group CL commands together, they may be compiled into a program object or submitted for interpretation during a batch process

  15. CL • Using what you know about abbreviated verbs and subjects, identify the function of the following AS/400 CL commands: • ADDLIBLE • CHGPGM • CLRPFM • RMVMSGD • DSPOBJAUT

  16. CL • What is a source physical file and what does it contain? • What steps would you follow to create a CL program? • When will the CL compiler not produce a CL program object?

  17. CL programming • Here are the four steps typically involved with creating a CL program: • Create a source physical file in your library to hold the source code for your CL programs  QCLSRC • For each specific program, add a member to the source physical file.  F6 • Type all the needed CL commands into the source member  SEU • Compile the CL program, creating a program object  option 14

More Related