1. Application Development on Power System (IBM i) School of Software Engineering Tongji University HUANGJie

2. NoSubjectHoursAbstractInstructor 1 Overview of IBM i 2 Server, Power System and Power System IBM i Huangjie 2 iOS fundamental 4 i OS & Basic Operation Huangjie 3 File system & object management 4 Object management concept and integrated file system Huangjie 4 Message management 2 Message & Its management Huangjie 5 Work management 4 Concepts of job, subsystem and library, job routing Huangjie 6 Administration ABC 2 Security, Storage & Restore Management Huangjie 7 Application Development 6 ILE development enviroment, RPG programming Huangjie 8 Database Development 4 Database on IBM i Huangjie 9 IBM i & SOA 2 SOA approach on IBM i Huangjie 10 Case Study 2 Csae Study Huangjie 11 Examination 2 Huangjie Syllabus

3. Chapter 5 Work Management Unit 1 Power System Foundation

4. Outline Agenda: – Work management concept and structure – Subsystem – Job – Major subsystem and job commands – Job description – Exercise/Practice – Question & Answer

5. Hardware Kernel OS Applications Direct access to hardware is not allowed! Machine Interface (MI) - or Technology Independent Machine Interface (TIMI) - logical not physical interface SLIC OS/400* System License Internal Code (SLIC) - insulate applications from underlying hardware - SLIC is hardware dependent! * called i5/OS on i5 systems Work management - TIMI 2015-11-295

6. OS/400 SLIC Hardware Machine Interface Security Database Device support Work management Work management - OS Functional Split 2015-11-296

7. Work Management Concept Work management is the core of the operation system. It provides functions necessary to control system operation and job processing on the system. A Job is a set of tasks performed on a computer system. With a job, any number of functions can be performed. Jobs may be requested by a single control language command, a series of CL commands, a single program (i.e., a CL program or a high-level language program such as an RPG program), or a series of programs. Work management controls batch jobs, interactive jobs and spooled jobs. 2015-11-297

8. Work Management Structure IBM i work management has three major levels in its structure. – System – Subsystem – Job entries System – IBM i system as a whole is defined by system values and network attributes. Both of which must be configured and established when the system is first set up. – Examples of system values are system time, date, the maximum number of activity levels of the system. – Examples of network attributes are system name, local network ID, and network server name. 2015-11-298

9. Work Management Structure (Continued) Both system values and network attributes can be retrieved and changed by CL commands. Command examples for system values: – Retrieve system values command: RTVSYSVAL – Retrieve System Value RTVSYSVAL SYSVAL (system-value-name) RTNVAR (CL-variable-name) – Change system value command: CHGSYSVAL – Change system value CHGSYSVAL SYSVAL (system-value-name) VALUE (new-value) Command examples for network attributes: – RTVNETA – Retrieve Network Attributes RTVNETA SYSNAME (CL-variable-name) LCLNETID(CL-variable-name) + NETSERVER (CL-variable-name) – CHGNETA – Change Network Attributes CHGNETA SYSNAME (system-name) LCLNETID (local-network-ID) + NETSERVER (network-ID) 2015-11-299

10. 术语 _ 选自《计算机操作系统教程 [ 张尧学 著 ] 》 JOB( 作业 ) ： – 在一次应用业务处理过程中，从输入开始到输出结束，用户要求计算机 所做的有关该次业务处理的全部工作。 – 作业由不同的顺序相连的作业步组成。 – 作业步是在一个作业的处理过程中计算机所做的相对独立的工作。 JOB( 作业 ): 比程序更广的概念 – 作业由程序、数据和作业说明书组成。 – 系统通过作业说明书控制程序和数据，使之执行和操作。 Process( 进程 ): – 并发执行的程序在执行过程中分配和管理资源的基本单位。 Thread( 线程 ) ： – 是进程的一部分，没有自己的地址空间，它和进程内的其他线程一起共 享分配给该进程的所有资源。 – 使用线程的好处是：在有多个任务需要处理时，减少处理机的切换时间， 且线程的创建和结束所需要的系统开销比进程的创建和结束开销少得多。 2015-11-2910

11. Work management objects MI Job Process Thread 2015-11-2911

12. Interactive Job Routing - Operator‘s View 2015-11-2912

13. Outline Agenda: – Work management concept and structure – Subsystem – Job – Major subsystem and job commands – Job description – Exercise/Practice – Question & Answer

14. Subsystem – Subsystems contain job entries where jobs are placed and processed. – Subsystems include IBM-supplied subsystems and user-created subsystems. – IBM-supplied subsystems include the QBASE, QCTL, QBATCH, QINTER, QSPL, and QCMN. – QBASE QBASE is the default subsystem that allows users to run all jobs when the system is first installed. The QBASE subsystem should be regarded only as a transitory subsystem because it is very inefficient to run all jobs in just one subsystem. As soon as the system is established up and running, you should use the CHGSYSVAL command to change the subsystems that run your jobs. 2015-11-2914

15. Subsystem (2) Subsystem – QCTL The subsystem that starts and ends other subsystems such as QBATCH, QINTER, QSPL and QCMN. QCTL also controls the functions of other subsystems. – QBATCH The subsystem contains job queues that allows batch jobs to be submitted and run. QBATCH arranges and manages the batch entries, job priorities, and running of active jobs. – QINTER The subsystem has workstation entries that allow interactive jobs to run simultaneously in this subsystem. – QSPL The subsystem has spooled job queue entries for spooled jobs. Example of spooled jobs are read and write spooled jobs. – QCMN The subsystem has communication entries for all communications jobs that are to run in this subsystem. 2015-11-2915

16. A specialized environment for handling a certain type of work or function, such as: - WRKSBS COMMUNICATIONS BATCH INTERACTIVE SPOOLING Subsystems 2015-11-2916

17. Subsystem Description (1/4) 2015-11-2917

18. Subsystem Description (2/4) 2015-11-2918

19. Subsystem Description (3/4) 2015-11-2919

20. Subsystem Description (4/4) 2015-11-2920

21. Outline Agenda: – Work management concept and structure – Subsystem – Job – Major subsystem and job commands – Exercise/Practice – Question & Answer

22. Job Type 2015-11-2922

23. Job Job Entries – The Job Entries are the depositories where jobs actually run. – Job Queue Entries are job queues that are normally defined and created in the subsystems that run batch jobs (i.e., QBATCH, QBATCH2) – Workstation Entries are entries that are defined in the subsystems that run interactive jobs (i.e., QINTER, QINTER2). Interactive jobs are run by users through workstation terminals. Subsystems must allow multiple workstation entries running multiple interactive jobs simultaneously. – Spooled job entries are job queues that are defined in the subsystem that run spooled jobs (i.e., QSPL). Spooled job entries allow reader and writer spooled jobs to run. – Communication entries are normally defined in the QCMN subsystem. They contain communications protocols and allow communications jobs to run. 2015-11-2923

24. Job identification 2015-11-2924

25. Job Life Cycle 2015-11-2925

26. Job Processing 2015-11-2926

27. Job Queue 2015-11-2927

28. Job Description 2015-11-2928

29. User Profile 2015-11-2929

30. Output of job - Job log (DSPJOBLOG) 2015-11-2930

31. Output of job – Spooled file (WRKSPLF) 2015-11-2931

32. Output of job – Spooled file (DSPSPLF) 2015-11-2932

33. Output of job – Output Queue (WRKOUTQ) 2015-11-2933

34. Output of job – Message Queue (WRKMSGQ) 2015-11-2934

35. Output of job – Message Queue (WRKMSGQ) 2015-11-2935

36. What everyone would like to have … 2015-11-2936

37. But what we do have 2015-11-2937

38. Outline Agenda: – Work management concept and structure – Subsystem – Job – Major subsystem and job commands – Exercise/Practice – Question & Answer

39. Major subsystem and job commands - Job GO CMDJOB – Lists all job related commands DSPJOBLOG – shows commands and related messages for a job that is still active when its job log has not been written. WRKJOB – works with or change information concerning a user job WRKACTJOB – works with performance and status information for the active jobs in the system. WRKSBMJOB – works with all jobs submitted from your work station, job, or user profile. WRKUSRJOB – works with a list of selected user jobs. CHGJOB – changes some of the attributes of a job. SBMJOB – allows a job that is running to submit another job to a job queue to be run later as a batch job. – The default subsystem for batch job is QBATCH DLYJOB – causes your current job to wait for a specified number of seconds, or until a specified time of day, before running resumes.

40. Major subsystem and job commands - Subsystem GO CMDSBS – Lists all subsystem related commands STRSBS – starts a subsystem using the subsystem description specified in the command ENDSBS – ends the specified subsystem (or all active subsystems) and specifies what happens to active work being processed. WRKSBS – allows you to work with each active subsystem in the system. WRKSBSD – shows a list of subsystem descriptions and allows you to change, delete, display, start, and end specified subsystem descriptions.

41. Outline Agenda: – Work management concept and structure – Subsystem – Job – Major subsystem and job commands – Exercise/Practice – Question & Answer

42. Exercise - System i work management Qualified Job Name is built up by? – Job Number + User Name + Job Name

43. Questions & Answer 2015-11-2943