Lecture 3 REVIEW of concepts security assistance profiles Library list

Slides:



Advertisements
Similar presentations
Week # 3 AS/400 Library List A library list is:
Advertisements

August 29, Accessing the iSeries and Some Commands.
iSeries Lecture 2 Technology independence Technology independence  change the underlying hardware architecture and add new functionality without disrupting.
Week # 2 - Agenda Types of AS/400 Objects Qualified/Unqualified Names
Hands-On Microsoft Windows Server 2003 Administration Chapter 5 Administering File Resources.
University of Southern California Enterprise Wide Information Systems Getting Started in R/3 Instructor: Richard W. Vawter.
Linux+ Guide to Linux Certification, Second Edition
Seneca College of Applied Arts & Technology
The AS/400 and the printing process
1 REVIEW Object types - ???? System security levels - ???? Current library - How is it assigned ???? How do you change it??? Qualified naming - What is.
Chapter 16 - Monitoring Hardware and Jobs
CS102 Introduction to Computer Programming
W1L1ops400.ppt1 Welcome! OPS400 students to the POWER SYSTEM Mid-Range Operating System.
Hands-On Microsoft Windows Server 2008
Sharing Resources Lesson 6. Objectives Manage NTFS and share permissions Determine effective permissions Configure Windows printing.
IBC233 Week 1 Updated Fall 2010 Homework? Finish Lab 1 – hand in compile listings of the two programs at the beginning of next week’s Lab Period!
1 Guide to Novell NetWare 6.0 Network Administration Chapter 12.
Hands-On Virtual Computing
Taught by Mohamed Kassim
L1C1introops400.ppt1 Welcome! OPS400 students to the AS/400, iSeries Mid-Range Operating System Used for Commercial applications and as powerful servers.
Mastering the AS/400, Third Edition, author Jerry Fottral 1 Week 2 The System The AS/400 is a multi-user, multi-tasking system -- a system on which many.
Chapter 16 Designing Effective Output. E – 2 Before H000 Produce Hardware Investment Report HI000 Produce Hardware Investment Lines H100 Read Hardware.
CHAPTER FOUR COMPUTER SOFTWARE.
Copyright © 2007, Oracle. All rights reserved. Managing Concurrent Requests.
Chapter Three The UNIX Editors. 2 Lesson A The vi Editor.
Chapter 2: Operating-System Structures. 2.2 Silberschatz, Galvin and Gagne ©2005 Operating System Concepts Chapter 2: Operating-System Structures Operating.
1 OPS650 Andre Berns. Welcome! OPS650 students to the follow up of OPS400 On the AS/400 Mid-Range Operating System.
INVITATION TO COMPUTER SCIENCE, JAVA VERSION, THIRD EDITION Chapter 6: An Introduction to System Software and Virtual Machines.
ICS124 Session 11 Introduction to AS/ By the end of this section, the student will be able to: Define the major difference between the AS/400 and.
L9C6ops400.ppt1 Device configuration Chapter 6 How to connect devices to the AS/400.
IBC233 Lecture 2 Updated Winter 2008 Agenda Test next Week – Jan 23 ISeries Architecture CL (Control Language) Library Lists Operations Navigator.
Welcome to BAC344! Business Applications using COBOL Andre Berns.
DBT544. DB2/400 Advanced Features Level Check Considerations Database Constraints File Overrides Object and Record Locks Trigger Programs.
Week 4 presentation! This week we will cover editing and the use of the on-board tools provided, SEU and PDM.
Chapter Three The UNIX Editors.
1 “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.
W6L1ops400.ppt1 Reviews. 2 Notation types? Difference ? Job commands ?Get help with CMD??? Menu What role does the user profile play?What is your job.
BA271 Week 6 Lecture Dave Sullivan. Goal for today… Status Report – Review where we are … Status Report – Review where we are … Begin learning about Microsoft.
Mastering the AS/400, Third Edition, author Jerry Fottral 1 Week 12 Lesson Overview Introduce the idea of object authorization and see how library and.
IBC233 Lecture 2 Updated Summer 2006 Agenda Review What’s ODIN doing? Library List Websphere –Filters.
Folio3 IPhone Training Session 2 Testing App on device Presenter: Imam Raza.
1 Week # 4 Introduction to PDM PDM is a workbench environment that lets programmers and system operators navigate the three levels of the AS/400’s object-based.
Hands-On Microsoft Windows Server 2008 Chapter 5 Configuring Windows Server 2008 Printing.
IBC233 Lecture 2 Updated Summer 2007 Agenda Real Estate Issues Review System Values What’s ODIN doing? Library List Websphere –Filters –Writing a CL.
IBC233 Week 2 Updated Fall 2011 Homework? Finish Lab 1 – Due Today! Send me an with your userid when you are done! Download and install software.
1 Welcome! DBT544 students to the iSeries, DB2 Universal Database And SQL interface.
Today’s Agenda Object Management Library List PDM (Programming Development Manager) SEU (Source Entry Utility)
Active-HDL Server Farm Course 11. All materials updated on: September 30, 2004 Outline 1.Introduction 2.Advantages 3.Requirements 4.Installation 5.Architecture.
Welcome to IBC233 Cindy Laurin And Russ Pangborn.
W1L2ops400.ppt1 Lecture 1 OPS400 AS/400 / iSeries / eSeries Mid-Range Operating System OS/400.
Welcome to IBC233 Cindy Laurin And Russ Pangborn.
Chapter 6 Chapter 6 - Summary.
Security and Security System Values
Objects, Libraries, and Library Lists
Lecture 2 REVIEW of concepts security assistance profiles Library list
Chapter 10 Backup and Recovery.
Chapter 2: System Structures
IBC233- iSeries Business Computing Summer 2006 Welcome!
Guide To UNIX Using Linux Third Edition
Starting and Stopping the AS/400
Chapter 13 Subsystems.
IBC233 Week 2 Updated Winter 2011
Handling Spooled Files and Printing Functions
Welcome to IBC233 Taught by Cindy Laurin.
Welcome to IBC233 Taught by Cindy Laurin.
Exploring the Power of EPDM Tasks - Working with and Developing Tasks in EPDM By: Marc Young XLM Solutions
Operating Systems Tasks 17/02/2019.
IBC233 Week 2 Updated Fall 2011.
Taught by Cindy Laurin And Mohamed Kassim
Welcome to IBC233 Cindy Laurin.
Presentation transcript:

Lecture 3 REVIEW of concepts security assistance profiles Library list authority L3C2ops400.ppt

AS/400 Architecture Object-based architecture The Machine Interface (MI) translates instructions from the logical machine (OS/400 and application programs) to the physical machine (the hardware). The MI insulates the logical machine from the physical There are many advantages to this:

Architecture cont’d Single level storage main and secondary memory (RAM & disk) are treated as a single mass no hardware oriented considerations (eg. Managing disk drives) because memory is managed by internal code, objects can be shared by different jobs.

Licensed Programs Licensed Internal Code Application Development Tools PDM (you have been using since the first lab) OfficeVision similar to MS-Office, but AS/400 based Communication Support Client Access Mocha Programming Languages Pascal, PL/1, Basic, RPG, C, C++, Cobol, Java, SQL, etc.

Commonly Used Function Keys F1 = Help F2 = Extended Help F3 = Exit command completely F4 = Prompt F5 = Refresh Screen F9 = Retrieve Previous Command F12 = Cancel current level and return to previous level in command F23 = more options F24 = more functions

Commonly Used Options on LIST type screens 2 = Edit 3 = Copy 4 = Delete 5 = Display 5* = Some cases Work With 6 = Print 7 = Rename 8 = display Description 9 = Save 12 = Work With 14 = Compile / Generate When applicable!

* On the AS/400 The * (asterisk or star) when used before a parameter value denotes a special value. Eg. *all, *libl, *curlib When the * is used after a parameter value, it is a wild card (just like in DOS) Eg. WRKUSRPRF DB400*

Using F4 and ? The ? is used the same way F4 is. Entered into a command field, it gives you the possible values for the field. Entered before a command, puts you in prompt mode for that command. Eg. ?CRTLIB

STORAGE HIERARGY Library: an object whose purpose is to ‘store’ and index other objects. ie. objects are ‘stored’ in libraries. Files: objects that store data Members: Source files have many ‘members’ each source program = one member Data Files: most common 1 member only exception multiple members (multi territory, multi company)

Hierarchy of Storing Objects When an object is created, it is stored in the library specified. If no library is specified, it is stored in *CURLIB (current library). If there is no current library, it is stored in QGPL library. Exception: Libraries, Device Descriptions and User Profiles are always stored in library QSYS.

Work with Members Using PDM File . . . . . . QCLSRC Library . . . . OPS234LIB Position to . . . . . Type options, press Enter. 2=Edit 3=Copy 4=Delete 5=Display 6=Print 7=Re 8=Display description 9=Save 13=Change text 14=Compile 15=Cr Opt Member Type Text ___ BIRTHDAY CLP ___ CH11TIM CLP Chapter 11 CL program demo version ___ LAB4CLP CLP Lab 4 CL program ___ SHELL CLP CL program shell

or GO CMD??? GO CMDDSP GO CMDWRK GO CMDACT GO CMDUSR CMDCPY Copy Commands CMDDSP Display Commands CMDWRK Work With Commands CMDLIB Library Commands CMDMSG Message Commands CMDOUTQ Output Queue Commands CMDUSRPRF User Profile Commands ETC. ETC

GO Verb Menu

Physical SECURITY Data Locked access All the digital information Damage control of processor, devices and media from fire, flood etc. Data All the digital information User Programs, O/S, Utilities, data integrity Object based / User based AS/400 uses a combination of both to ensure the MOST secure environment to operate in.

DATA SECURITY cont’d System Level - system values / levels 10 - 50 user profiles - unique and password protected controls authorities, ownership, environment, user group QSECOFR, QSECADM, QSYSOPR, QPGMR, QUSER etc… Object - access authority to object for each user authority lists for groups - *ALL *CHANGE *USE *EXCLUDE

special AUTHORITIES required for CERTAIN FUNCTIONS *ALLOBJ *AUDIT *IOSYSCFG *JOBCTL *NONE *SAVSYS *SECADM *SERVICE *SPLCTL See page 22 of text book

Authorization lists - AUTL OBJECT AUTHORITY Display Authorization List Object . . . . . . . : OPSPRF Owner . . . . . . . : ADMIN Library . . . . . : QSYS Primary group . . . : *NONE Object List ----------Object----------- User Authority Mgt Opr Mgt Exist Alter Ref ADMIN *ALL X X X X X X MOOGK *ALL X X X X X ABERNS *ALL X X X X X DMENKEN *ALL X X X X X LYDIA_LI *ALL X X X X X CREER *ALL X X X X X *PUBLIC USER DEF X Press Enter to continue. F3=Exit F11=Display data authorities F12=Cancel F15=Display authorization list objects F17=Top F18=Bottom

Authorization lists - AUTL DATA AUTHORITY Display Authorization List Object . . . . . . . : OPSPRF Owner . . . . . . . : ADMIN Library . . . . . : QSYS Primary group . . . : *NONE Object ---------------Data--------------- User Authority Read Add Update Delete Execute ADMIN *ALL X X X X X MOOGK *ALL X X X X X ABERNS *ALL X X X X X DMENKEN *ALL X X X X X LYDIA_LI *ALL X X X X X PANGBORN *ALL X X X X X CREER *ALL X X X X X Press Enter to continue. F3=Exit F11=Nondisplay detail F12=Cancel F15=Display authorization list objects F17=Top F18=Bottom

How the AS/400 finds Objects When an object is created, it is created ‘in’ a particular library. To access an object, the AS/400 needs to know what library the object is in. (CL) Commands prompt you for the object name and library name. *LIBL is the default entry for a library parameter name request

Qualified Name vs SIMPLE Name If you specify an object name and library, it is called a qualified name) e.g. Call OPS234LIB/PGM01 When you use the object name by itself it is called a simple name and then the *LIBL is used to find the object .e.g. Call PGM01

Library Lists type *LIBL A list of Libraries, in order of importance Similar to the DOS ‘Path’ concept Each Job has it’s own library list (Can be inherited) It determines where a Job finds Objects when SIMPLE naming is used

Library Lists cont’d Each Library List consists of 4 parts: System Libraries (up to 15) Product Libraries (none, 1 or 2) Current Library(1 only) User Library ( up to 25) To view your library list - DSPLIBL

Library List cont’d

Library List cont’d Determine where a Job finds Objects when SIMPLE NAMING is used v.s. ???????????????

How / when is a Library List created? When you sign on (start a session), your library list is built from: QSYSLIBL (system value) QUSRLIBL (system value) Current library from User Profile Associated JOB description *JOBD initial user list part INHERETED from the parent job (process). Product libraries are added as needed by the system

System Values These values define what the default values will be. You can’t change them, but you can look at them. See page 4 of text for examples

System Values are used for Control and configuration attributes System values are AS/400 attributes that allow each installation to customize the machine to the organization’s own needs and specifications. -The categories of system values include : Date and time System control Library list values Editing values Allocation values Security values Storage values Message and logging values DSPSYSVAL QDATE

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 ===> DSPSYSVAL <F4> F3=Exit F4=Prompt F9=Retrieve F12=Cancel F13=Information Assistant F23=Set initial menu

Display System Value (DSPSYSVAL) Type choices, press Enter. ____________ F4 System value . . . . . . . . . . QABNORMSW, QACGLVL... Output . . . . . . . . . . . . . * *, *PRINT Specify Value for Parameter SYSVAL Type choice, press Enter. System value . . . . . . . . . . QABNORMSW QAUDLVL QACGLVL QAUTOCFG QACTJOB QAUTORMT QADLACTJ QAUTOSPRPT QADLSPLA QAUTOVRT QADLTOTJ QBASACTLVL QALWOBJRST QBASPOOL QALWUSRDMN QBOOKPATH QASTLVL QCCSID QATNPGM QCENTURY QAUDCTL QCFGMSGQ QAUDENDACN QCHRID QAUDFRCLVL QCHRIDCTL + F3=Exit F5=Refresh F12=Cancel F13=How to use this display F24=More keys

SECURITY RELATED SYSTEM VALUES QAUDJRN QAUDLVL QCRTAUT QDSPSGNINF QMAXSIGN QMAZSGNACN QLMTDEVSSN QINACTIT QINACTMSGQ QDSCJOBITV QUPSMSGQ QUPSDLYTIM QPWRRSTIPL QSECURITY ........

Display System Value (DSPSYSVAL) Type choices, press Enter. System value . . . . . . . . . . > QSECURITY... Output . . . . . . . . . . . . . * *, *PRINT <ENTER> Display System Value System value . . . . . : QSECURITY Description . . . . . : System security level System security level . . . : 40 10=Physical security only (no longer supported) 20=Password security only 30=Password and object security 40=Password, object, and operating system integrity 50=Password, object, and enhanced operating system integrity 5 LEVELS USER DEPENDEND AND ASSIGNED BY THE SYSADM

AUTHORITY System value . . . . . : QCRTAUT Description . . . . . : Create default public authority Create default public authority . . . . . : *CHANGE *CHANGE *ALL *USE *EXCLUDE

Assistance Levels Determines how much information is displayed and how it is formatted. Basic, Intermediate, Advanced, default on USRPRF Page 19 in text. Try it out for yourself using the WRKSPLF command and function key F21

Display System Value System value . . . . . : QASTLVL Description . . . . . : User assistance level Assistance level . . . : *BASIC *BASIC *INTERMED *ADVANCED .............................................................................. : QASTLVL - Help : : : : Assistance level. Specifies the level of assistance available to users : : of the system. This system value is used to tailor the level of : : displays available for users of the system. Displays intended for less : : experienced users provide a higher level of assistance than do displays : : intended for expert users. : : A change to this system value takes effect the next time a user signs : : on. The shipped value is *BASIC. : : Bottom : : F2=Extended help F3=Exit help F10=Move to top F12=Cancel : : F13=Information Assistant F14=Print help : :............................................................................: Press Enter to continue. F3=Exit F12=Cancel

USER and the associated classes ................................................................ : User Class - Help : : : : The type of user. User class is one of the following: : : o *PGMR - Programmer : l o *SECADM - Security administrator : : o *SECOFR - Security officer : o *SYSOPR - System operator o *USER - User A user can belong to a group and obtains all the group assigned authorities and securities

USER and the associated classes Display User Profile - Basic User profile . . . . . . . . . . . . . . . : DB400A01 Previous sign-on . . . . . . . . . . . . . : Sign-on attempts not valid . . . . . . . . : 0 Status . . . . . . . . . . . . . . . . . . : *ENABLED Date password last changed . . . . . . . . : 01/08/01 Password expiration interval . . . . . . . : *SYSVAL Set password to expired . . . . . . . . . : *NO User class . . . . . . . . . . . . . . . . : *PGMR Special autho ................................................................ Group profile : User Class - Help : Owner . . . : : Group authori : The type of user. User class is one of the following : Group authori : o *PGMR - Programmer : Supplemental : o *SECADM - Security administrator : Assistance le : o *SECOFR - Security officer : Current libra : o *SYSOPR - System operator : o *USER - User : Press Enter t : F2=Extended help F10=Move to top F12=Cancel : : F13=Information Assistant F20=Enlarge F24=More keys : F3=Exit F12 : : (C) COPYRIGHT :..............................................................:

DSPJOBD QBATCH First page of job attributes Display Job Description System: ODIN Job description: QBATCH Library: QGPL User profile . . . . . . . . . . . . . . . . . . : QPGMR CL syntax check . . . . . . . . . . . . . . . . : *NOCHK Hold on job queue . . . . . . . . . . . . . . . : *NO End severity . . . . . . . . . . . . . . . . . . : 30 Job date . . . . . . . . . . . . . . . . . . . . : *SYSVAL Job switches . . . . . . . . . . . . . . . . . . : 00000000 Inquiry message reply . . . . . . . . . . . . . : *RQD Job priority (on job queue) . . . . . . . . . . : 5 Job queue . . . . . . . . . . . . . . . . . . . : QBATCH Library . . . . . . . . . . . . . . . . . . . : QGPL Output priority (on output queue) . . . . . . . : 5 Printer device . . . . . . . . . . . . . . . . . : *USRPRF Output queue . . . . . . . . . . . . . . . . . . : *USRPRF Library . . . . . . . . . . . . . . . . . . . : More... Press Enter to continue.

Operations Navigator the GUI Interface

Installing Client Access with Operations Navigator from seneca home page select ACS select info center select server related info select AS400 select client access setup instructions The instructions there might help you http://acs.senecac.on.ca/as400/clientaccess.html

For Next Week Study chapter 2 Read Chapter 3 Be present AT and DO your LAB