W1L1ops400.ppt 1

Welcome!

OPS400 students

to the

POWER SYSTEM

Mid-Range Operating System

2

Who Am I? Andre Berns

Over 38 Years of Industry Experiencein system design

and software developmentwith Mainframes, Midrange and PC’s

on LARGE, MID, MINI, MICROsize computers

(AS/400 is the BEST!)

iSeries, eSeries, Series I and the newest Power Systems

3

Intended Course Structure• 2 hours of lecture

• Followed by 2 hours of labs

• The purpose of the lab is to practice what you learned in the lecture.

• It is the hands-on, practical side of the course.

• Attendance and completion of the labs will be a key factor in completing the course successfully.

4

Lecture and Lab Notes

• Lecture notes will be available from my Home Page.

• Some Labs will be available from my Home page or taken directly from the Text Book.

• Please print the lecture or lab notes, when found on the WEB pages, ahead of time and bring them to class.

5

Do you want to do well?• Show up for Lectures

• Complete the Labs, MARKS!

• Do the assignments, a MUST!

• Do the required reading

• Do the Review questions and labs from your text book, they serve both to re-enforce and as practice

• Ask Lots of Questions both during lecture and labs

6

Material Covered

• All chapters in the text book.

• Two tests– All tests will be conducted in the labs– Both tests will include material from chapter 1

onward including all chapters covered up to that date.

7

Material Covered Cont’d

• Assignments (to be determined)– Progressive in nature and knowledge base.– Geared towards specific chapters.

• One Final Exam

8

What is the “Power Systems”?

It is the latest name IBM uses to qualify their Midrange Computer

What does midrange mean?

In general, larger than a PC and smaller than a Mainframe!

9

What is an AS/400?

• IBM’s “Application System”/400• Multi-user, multi-tasking• Is most often used by a company to run their daily

business transactions• Can be used for special applications within a large

organization• Uses Single-level storage concept • RAM - DASD (seamless)

What is in a name?The AS/400 has been called by several

different names over its life cycle

AS/400 , iSeries, eSeries, “Series I” and now

“Power Systems”

These systems all use the OS/400 operating system progressively upgraded to reflect the

latest features

10

11

Industry Examples

• Sprint Canada• Grand and Toy• Canadian Tire• Microsoft !!• Praxair• See IBC233 web page for list of other companies

using the AS/400 (these are just the ones we know about!)

12

Why does a company use an AS/400?

• Cost effective

• Reliable

• Hundred’s of thousands applications available

• Easily upgraded as business grows

• Supports state-of-the-art technology

• Doesn’t require a large support staff

13

Why are we studying the AS/400?

There are hundreds of thousands of them out there.

98% of Fortune 100 Companies have an AS/400

Seneca is one of the few colleges to offer AS/400 courses, this makes you marketable!

Jobs! Jobs! Jobs!

14

Capability Comparison

PCMidRange

Main Frame

15

HistorySystem 3

1969

S/321975

S/341977

S/381978

S/361983

AS/4001988

iSeries2001

eSeriesPower Systems ……

16

Seneca Network (simplified)ODIN

(AS/400)To be decommissioned

ZEUS(AS/400)

PHOBOS(RS/6000)

FireWall

PCs atHome

PCs inthe Lab

17

Connectivity Software

• Client Access (used here – selectively - online)

• Mocha (use from home - online)

• RDS ( IBM Rational Developer for System I – offline / online)

Software that allows you to connect your PC to the AS/400 using communications.

18

How To Download the Mocha Software to Your PC

• Use the ACS link

•Download

•As/400

19

AS/400 vs. Unix - Terminology reference

• Attributes• Authorities• Current library• Command language programs• Command line entry • Database or IFS• Device description• Jobs• Library• library list’s• Object• Operations Navigator• QSYS• Subsystems• User profile *USRPRF

• Properties• Permissions• Working directory• Scripts• Command line interface - CLI• File system• Device special files, /dev• Processes / Tasks• Directory• Access path, $PATH• Files• Windowing system• Root, /• Shell• /etc/profile, .profile

AS/400 Unix

W1L2ops400.ppt 20

Lecture 1OPS400

AS/400 / iSeries / eSeries

Mid-Range

Operating System

OS/400

21

“System”

• The AS/400 is the “system”

– “The system is down”– “The system is slow today”

22

OS400

AS/400 Operating System Object-Based

- User Profiles

– Job Queues– Files– Programs

Not only does it control all the activity on the AS/400, but it also incorporates many features that would be separate software components on other systems.

23

Licensed Programs• Application Development Tools

– PDM (you will see this in the first lab)

• OfficeVision

– similar to MS-Office, but AS/400 based

• Communication Support

– Client Access (command line and GUI based)

• Programming Languages

– Pascal, PL/1, Basic, RPG, C, C++, Cobol, Java, SQL, HTML, etc.

24

System Values are control and configuration attributes. They are used to customize a system to the needs and specifications of an organization.

Some are

Date and time.Editing.system control.user control.etc. etc

DSPSYSVAL - WRKSYSVAL - CHGSYSVAL

25

“User”

• A person who “uses” the AS/400• You are all “Users” each with an unique

Userid• A Userid identifies you to the system when

you signon or run a job• Each Userid has a User Profile which

describes the user attributes, one of which is authorities.

jobpresentation.ppt 26

What is it ?

Types of ?

How invoked ?

A JOB

27

• A “job” is any and every piece of work / activity on the AS/400 similar to a “Process” in Unix.

- System functions- Utilities

- User tasks- etc.

28

It consists of one or more tasks executed either successivelyor simultaneous while sharing resources.

lecturing

learning

meeting

greeting

29

INTERACTIVE (USER)

High run time priority on job queue (20)

QUICK response

Low resource requirement (memory – disk)

Some Types of jobs

BATCH

NO interactivity (only messaging)

Low run time priority on job queue (50)

High resource requirement (memory – disk – media)

CLI – Command line interface Batch, Daemons, cron

In UNIX

30

“Interactive Jobs”also called sessions

• it begins when a user signs on to the system and ends when they sign off.

• Has interaction between the user and the AS/400, similar to a conversation

(a polite conversation!).

• Input entered via the work station.

31

“Batch Jobs”

• Runs in the background.

• No interactive input from the screen, receives data from files or data communication.

• Generally uses a lot of resources.

• Submitted / initiated by ANY job e.g. a program compile

• Communicate with the system through messaging.

32

JOBS - HOW INVOKED?

• Signing on and starting an interactive session

• Called by another JOB. (spawned)

• Automatic system function

• SCHEDULED once or repetitively

33

Job Inheritance

• Attributes / properties are passed on from the initiating / spawning job

• The initial Job (starting session) inherits attributes from other sources such as System values, values from a user profile and from a job description are retrieved.

34

“Jobs and subsystems”

• Each Job runs in a specific subsystem based on type.

• A subsystem is where the system brings together and prioritizes the resources needed to process work of LIKE type to optimize performance.

35

System vs Subsystems

• Access the WoRK with ACTive JOB Command to see the difference

• System is the entire AS/400

• Sub-System is a logical grouping of system resources designed to process jobs with similar requirements and demands on the resources.

36

“Subsystem”

• Each (there are many) has been allocated a share of the total resources available in the system based on requirements.

• A Job runs in a specific subsystem.

• A subsystem is where the system brings together the resources needed to process work of LIKE type. Enable better performance tuning.

• Described / defined in subsystem descriptions. (*SBSD).

• Most are started at IPL time.

37

There are many subsystems the most common are

QCTL

QINTER

QBATCH, QBATCH2, etc

QCMN

QSPL

38

the best known are

• Interactive jobs run in subsystem QINTER

• Batch jobs run in subsystem QBATCH

39

Queues

• A queue is a line-up! A place where things wait.

• Examples of AS/400 queues:

– job queues: where batch jobs wait

– message queues: where messages wait

– output queues: where spool files wait to print

• Controlled by– Run time priority

– Position in Stack

– Etc

40

The AS/400 is easy to use

• Menu driven

• Lots of built-in help

• Built-in security

41

Originally the AS/400 is “Green Screen”

is 5250 emulation

• Block mode v.s. Character mode

• Green screen v.s. GUI (Graphical User Interface– You can’t point and click in emulation mode!– You must use the TAB keys to go from field to

field– Use the <enter> key to “send”.

42

The Signon Screen

• The first level of security, it keeps out unauthorized people

• It requires a valid userid and password ( see your sticky label)

• Always remember to signoff if you are going to leave your computer. If you don’t, someone could come along and clobber your work!

43

“Green Screen”

44

AS/400 Screen Types

• Menus: includes menu selections, command line, function keys, header info

• Entry: e.g. Command Prompt screen which includes parameter description, input fields, function keys, header info

• Information screens: e.g. help screens• List screens: e.g. ‘work with’ screens

includes list of objects or members, options, command line, function keys, header info.

45

MAIN AS/400 Main Menu System: ODIN Select one of the following: 1. User tasks 2. Office tasks 3. General system tasks 4. Files, libraries, and folders 5. Programming 6. Communications 7. Define or change the system 8. Problem handling 9. Display a menu 10. Information Assistant options 11. Client Access/400 tasks 90. Sign off Selection or command ===> go major . F3=Exit F4=Prompt F9=Retrieve F12=Cancel F13=Information Assistant F23=Set initial menu

MENU SCREEN

46

Specify Members to Work With Type choices, press Enter. File . . . . . . . . . . QCLSRC Name, F4 for list Library . . . . . . . . ABERNS *LIBL, *CURLIB, name Member: Name . . . . . . . . . *ALL *ALL, name, *generic* Type . . . . . . . . . *ALL *ALL, type, *generic*, *BLANK F3=Exit F4=Prompt F5=Refresh F12=Cancel

ENTRY SCREEN

47

........................................................................…………………………………………...... : All Spooled Files - Help : : : : The Work with All Spooled Files display shows all (or a specified : : portion) of the spooled files that are currently on the system. The : : purpose of this display is to allow you to find spooled files on the : : system. This display is shown when you specify the assist level : : parameter as intermediate, ASTLVL(*INTERMED) on the WRKSPLF command. : : : : You can type an option number next to one or more files. When you : : then press the Enter key, the function associated with the selected : : option is performed for each of the selected files. : : : : If you press the Enter key from this display without typing any : : other data, you are returned to the previous menu or display. : : : : You can type parameters in the command line if you want to override : : the defaults for the options you typed. You can type parameters : : More... : : F3=Exit help F10=Move to top F12=Cancel F13=Information Assistant : : F14=Print help : : : :.....................................................................……………….… .:

INFORMATION SCREEN

48

Work with All Spooled Files LIST SCREEN Type options, press Enter. 1=Send 2=Change 3=Hold 4=Delete 5=Display 6=Release 7=Messages 8=Attributes 9=Work with printing status Device or Total Cur Opt File User Queue User Data Sts Pages Page Copy __ APVENDOR ABERNS ABERNS RDY 4 1 __ OP400PF ABERNS ABERNS RDY 4 1 __ ARTRANPF ABERNS ABERNS RDY 3 1 __ ARUPDT ABERNS ABERNS RDY 6 1 __ ASSIGN2 ABERNS ABERNS RDY 4 1 __ ARTRANS ABERNS ABERNS RDY 6 1 __ QPDZDTALOG ABERNS ABERNS RDY 2 1 __ PGM400D03 ABERNS ABERNS RDY 4 1 __ INVTRY ABERNS ABERNS RDY 3 1 More... Parameters for options 1, 2, 3 or command ===> ______________________________________ F3=Exit F10=View 4 F11=View 2 F12=Cancel F22=Printers F24=More keys

49

CL - Control Language (like scripting)

Used from the command line - interactively

or

in CL programs (Scripting in UNIX) which can be called from

- the command line

- A Command directly

- From within other programs in either batch or interactive mode

50

“Objects”

• anything on the AS/400 that has a name and takes up space in storage and is not of a temporary nature and has action”

• on Unix/Windows, everything is a file• on AS/400, everything is an object• on Windows, files have extensions (.txt)• on AS/400 objects are of TYPE and subtype• Common object types include:

– libraries, files, job queues, programs

51

*ALL *CTLD *AUTL *DEVD *DOC *DTAARA *CMD *DTAQ *FILE *LIND *MENU *MSGQ *JOBQ *LIB *OUTQ *QRYDFN *SBSD *PGM *USRPRF

Some OBJECT type identifiers are

(special values)

52

Data Storage Hierarchy

Library

Objects

Members contain data

53

“Libraries”

• Library: an object whose purpose is to ‘store’ and index other objects. ie. objects are ‘stored’ in libraries.

• Exactly like a directory in Unix/Windows however you do not have libraries within libraries on the AS/400 (one exception).

54

Files - type *FILE

• Are objects that store data

subtypes / attribute• PF-DTA DATA file

ie. customer file: customer #, address,billing info etc. for each customer

• PF-SRC SOURCE file special file that stores a programmer’s source code (scripts)

55

File Members

• Source files have many ‘members’

• one member for each source (script) program

• PDM (Prog Dev Mgr) gives easy access to a programmer’s stuff (libs/files/mbrs)

56

Main Menu - GO MAIN

57

Major Menu - GO MAJOR

58

Verb Menu GO VERB

59

Commands Menu - Clear - GO CMDCLR

60

Clear File Example

Using PROMPTing

61

Clear Physical File Command

62

‘?’ in Member Parameter

63

Definition of the Member Parameter (Field Level Help)

64

Definition of the CLRPFM Command (Extended Help)

65

The Lab 1 Objectives are

• Get you familiar with AS/400 green screens, using menus etc.

• Review some of the definitions covered in lecture (user profile, jobs, subsystem, screen types, accessing help)

• Set up your stuff for later labs (a file for you to store your programs)

66

What to do next

• Read/Study Chapter 1 of the text

• Install C/A and or Mocha on your PC at home (if you have one)

67

What to do next

• In the labs we use – Client Access– Navigator– WDSc (Websphere Development Studio client)

– RDS

• At Home– Install Mocha on your PC at home (if you

have one)