DOCSLIB.ORG

Using IPCS with MVS/ESA Version 5

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

SYSTEM BY TOM BRYANT STRATEGIES MVS/XA/ESA Problem Solving: Part I — Using IPCS With MVS/ESA Version 5 PCS for MVS/ESA Version 5 has come a long way since I first used it in 1983 at the prompting of an exuberant IBM customer engineer. IPCS IPCS for MVS/ESA continues to move toward a fully panel-driven environment, although in Version 5 offers many Isome situations, I find using IPCS commands easier. capabilities, including the ability to scan for unformatted storage dumps. This article Future articles will examine the environ- easily in batch mode as well as in an ISPF mental record editing and printing program foreground session. I also wanted a CLIST examines the many (EREP), one-page MVS/XA/ESA abend that was well-documented with easy-to-use facilities of IPCS, analysis, advanced SVCDUMP analysis, parameters. Finally, I wanted a CLIST that slip traps and GTF tracing, and standalone does not hang onto dump directory and IPCS and includes some dump analysis. print dataset allocations when completed, as of the author’s favorite IPCS stands for Interactive Problem the IBM BLSCDDIR CLIST does. Control System, although most people IPCS commands. (myself included) use it just for looking at IPCS CLISTS FOR MVS/ESA unformatted storage dumps. IPCS will process VERSION 4.3 AND ABOVE SVCDUMPs which are dumps usually pro- The #IPCSTJB CLIST is the mainline duced with the abend (SVC 13) issued by your CLIST that you execute to establish an IPCS program or the system. Other unformatted session (see Figure 1). If you are invoking dumps that IPCS will produce include an #IPCSTJB for the first time, the NEW CLIST application unformatted dump allocated keyword parameter indicates that you will through the SYSMDUMP DD statement and dynamically create a VSAM dump directory the standalone dump produced by the stand- using the value of the VOL CLIST keyword alone dump program. parameter. The BATCH keyword will allow IPCS has the ability to process generalized you to run the #IPCSTJB CLIST in batch trace facility (GTF) data both externally and (where ISPF LIBDEF commands need not be within the dump. IPCS has the ability to look performed and initial SETDEF parameter at live system storage, although only for your favorites of mine are set). I have been unable address space; you can’t look at any private to pass these SETDEF commands to IPCS storage in another address space. when running as an ISPF application. I usual- IBM provides the BLSCDDIR CLIST in ly do a certain amount of IPCS batch process- the library SYS1.SBLSCLI0 to initiate an ing before using the ISPF interface due to per- IPCS session. If you are at MVS/ESA Version formance reasons covered later in this article. 4.3 or above, you can now initialize IPCS I have added keyword parameters of under ISPF — this makes IPCS much easier DDIRPRI and DDIRSEC to the #IPCSTJB to use as a full-fledged ISPF application. I CLIST to allow the user to determine how took the ideas presented in the BLSCDDIR many cylinders are necessary for the primary CLIST and created my own IPCS startup allocation of the IPCS VSAM dump directory CLIST. I wanted a CLIST that could be run and for the secondary allocation. Most of the TECHNICAL SUPPORT OCTOBER 1996 SYSTEM STRATEGIES Figure 1: #IPCSTJB: Clist to Get Into {Access} IPCS ELSE ALLOCATE F(IPCSDDIR) DSNAME(‘&SYSUID..DDIR.DUMP’) SHR REUSE IF &LASTCC GT 0 THEN + PROC 0 BATCH NEW VOL(UCB999) DDIRPRI(90) DDIRSEC(50) DEBUG DO /**************************************************************/ WRITE /* */ WRITE &SYSUID..DUMP.DDIR NOT FOUND /* #IPCSTJB: IPCS ALL-PURPOSE INITIALIZATION CLIST */ WRITE SPECIFY #IPCSTJB NEW /* */ FREE F(IPCSPRNT /* */ EXIT /* BATCH ==> POSITIONAL OPERAND TO INDICATE IPCS BATCH */ END /* EXECUTION (ISPF DIALOG IS DEFAULT) */ ISPEXEC LIBDEF ISPPLIB DATASET ID(‘SYS1.SBLSPNL0’) /* */ ISPEXEC LIBDEF ISPMLIB DATASET ID(‘SYS1.SBLSMSG0’) /* NEW ==> CREATE NEW IPCS VSAM DUMP DIRECTORY */ ISPEXEC LIBDEF ISPTLIB DATASET ID(‘SYS1.SBLSTBL0’) /* (DEFAULT IS TO USE EXISTING DIRECTORY) */ ISPEXEC LIBDEF ISPSLIB DATASET ID(‘SYS1.SBLSKEL0’) /* */ ISPEXEC SELECT PGM(BLSGLIBD) PARM(PANEL(BLSPPRIM)) + /* VOL ==> KEYWORD OPERAND TO SPECIFY WHERE IPCS VSAM */ NEWAPPL(BLSG) PASSLIB /* DUMP DIRECTORY IS TO RESIDE */ ISPEXEC LIBDEF ISPPLIB /* */ ISPEXEC LIBDEF ISPMLIB /* DDIRPRI ==> IPCS DUMP DIRECTORY PRIMARY ALLOCATION IN */ ISPEXEC LIBDEF ISPSLIB /* CYLINDERS (IF NEW DIRECTORY SPECIFIED) */ ISPEXEC LIBDEF ISPTLIB /* */ FREE F(IPCSDDIR,IPCSPRNT) /* DDIRSEC ==> IPCS DUMP DIRECTORY PRIMARY ALLOCATION IN */ EXIT /* CYLINDERS (IF NEW DIRECTORY SPECIFIED) */ END /* */ /* DEBUG ==> SHOW DIAGNOSTICS IF CLIST PROBLEMS */ IF &BATCH EQ &STR(BATCH) THEN + /* */ DO /**************************************************************/ IF &STR(&SYSISPF) EQ &STR(ACTIVE) THEN + DO CONTROL NOFLUSH NOLIST NOMSG WRITE #IPCSTJB BATCH CLIST MUST NOT BE EXECUTED UNDER ISPF FREE F(IPCSDDIR,IPCSPRNT) IF &DEBUG EQ &STR(DEBUG) THEN + EXIT CONTROL CONLIST SYMLIST LIST MSG END IF &NEW EQ &STR(NEW) THEN SET &DMPSTAT EQ &STR(NEW) WRITE #IPCSTJB CLIST BATCH EXECUTION ELSE SET &DMPSTAT EQ &STR(EXISTING) WRITE &SYSUID..DDIR.DUMP DUMP DIRECTORY STATUS IS &DMPSTAT WRITE DATASET &SYSUID..IPCSPRNT WILL BE CREATED DELETE ‘&SYSUID..IPCSPRNT’ IF &NEW EQ &STR(NEW) THEN + ALLOC F(IPCSPRNT) DA(‘&SYSUID..IPCSPRNT’) + DO NEW SPA(20 10) CYL REL REUSE %#IPCSDDR VOL(&VOL) DDIRPRI(&DDIRPRI) DDIRSEC(&DDIRSEC) &DEBUG IF &BATCH NE &STR(BATCH) THEN + END DO ELSE ALLOCATE F(IPCSDDIR) DSNAME(‘&SYSUID..DDIR.DUMP’) SHR REUSE IF &STR(&SYSISPF) EQ &STR(NOT ACTIVE) THEN + IF &LASTCC GT 0 THEN + DO DO WRITE #IPCSTJB NOBATCH CLIST MUST BE EXECUTED UNDER ISPF WRITE FREE F(IPCSDDIR,IPCSPRNT) WRITE &SYSUID..DUMP.DDIR NOT FOUND EXIT WRITE SPECIFY #IPCSTJB NEW END FREE F(IPCSPRNT WRITE #IPCSTJB CLIST ONLINE EXECUTION EXIT WRITE &SYSUID..DDIR.DUMP DUMP DIRECTORY STATUS IS &DMPSTAT END WRITE DATASET &SYSUID..IPCSPRNT WILL BE CREATED IPCS NOPARM IF &NEW EQ &STR(NEW) THEN + SETDEF ACTIVE LENGTH(200) FLAG(ERROR) + DO DISPLAY(MACHINE,REMARK,STORAGE,SYMBOL) + %#IPCSDDR VOL(&VOL) DDIRPRI(&DDIRPRI) DDIRSEC(&DDIRSEC) &DEBUG NOCONFIRM NOVERIFY END END Figure 2: #IPCSDDR: Allocate and Initialize New IPCS VSAM CONTROL NOFLUSH NOLIST NOMSG IF &DEBUG EQ &STR(DEBUG) THEN CONTROL SYMLIST CONLIST MSG Dump Directory PROC 0 VOL(UCB999) DDIRPRI(90) DDIRSEC(50) DEBUG DELETE ‘&SYSUID..DDIR.DUMP’ CLUSTER /**************************************************************/ /* */ DEFINE CLUSTER(NAME(‘&SYSUID..DDIR.DUMP’) + /* #IPCSDDR: CLIST TO DEFINE IPCS VSAM DUMP DIRECTORY */ VOLUME(&VOL) + /* (INVOKED BY THE #IPCSTJB CLIST) */ INDEXED + /* */ FREESPACE(10,10) + /* */ REUSE + /* VOL ==> KEYWORD OPERAND TO SPECIFY WHERE IPCS VSAM */ IMBED + /* DUMP DIRECTORY IS TO RESIDE */ REPLICATE + /* */ SHAREOPTIONS(1,3)) + /* DDIRPRI ==> IPCS DUMP DIRECTORY PRIMARY ALLOCATION IN */ INDEX(NAME(‘&SYSUID..DDIR.DUMP.INDEX’) + /* CYLINDERS (IF NEW DIRECTORY SPECIFIED) */ CYLINDERS(2,2) + /* */ CONTROLINTERVALSIZE(4096)) + /* DDIRSEC ==> IPCS DUMP DIRECTORY PRIMARY ALLOCATION IN */ DATA(NAME(‘&SYSUID..DDIR.DUMP.DATA’) + /* CYLINDERS (IF NEW DIRECTORY SPECIFIED) */ CYLINDERS(&DDIRPRI,&DDIRSEC) + /* */ KEYS(128,0) + /* DEBUG ==> SHOW DIAGNOSTICS IF CLIST PROBLEMS */ RECORDSIZE(384 3072)) /* */ /* */ /* APAR OY62871 - FIX CISIZ SPECIFIED FOR INDEX AND DATA */ IPCSDDIR ‘&SYSUID..DDIR.DUMP’ /* APAR OW13537 - SPECIFY CISIZE(4096) FOR INDEX ONLY */ /* (LET DATA TAKE VSAM DEFAULT) */ /* */ ALLOCATE FILE(IPCSDDIR) DSNAME(‘&SYSUID..DDIR.DUMP’) SHR REUSE /**************************************************************/ t i m e, my defaults will suffice (unless you are processing DB2 allow you to free IPCS print dataset allocation in order to rename the SVCDUMPs or standalone dumps, in which case, you will need much IPCSPRNT dataset to your choosing (see Figure 3). more space). Now that we have a tool for IPCS dump processing, we first have to The #IPCSTJB CLIST will invoke the #IPCSDDR CLIST only get the dump from the dump dataset to DASD. If the dump is in one of when the NEW parameter has been selected to create a new IPCS the system dump datasets (SYS1.DUMP?? where ?? is a number such VSAM dump directory (see Figure 2). The #IPCSDDR CLIST takes as 00 through 99) all you have to do is use IEBGENER to copy the care of this IPCS VSAM dump directory allocation using the same dump to your dump dataset. The SYS1.DUMP?? datasets must be key wo rd command names as #IPCSTJB. This is all pretty stra i g h t- a l l o c at e d LRECL of 4160, BLKSIZE of 4160 and RECFM F or FB, fo rward. The #IPCSTRM CLIST is only needed in a batch IPCS job to besides DSORG of PS. The pro blem inherent with using the TECHNICAL SUPPORT OCTOBER 1996 SYSTEM STRATEGIES Figure 3: #IPCSTRM: Issue IPCS END Command and Free Files Figure 4: Load Standalone Dump From Tape (Only Needed for Batch Jobs) //SADLOAD EXEC PGM=IEBGENER, // REGION=5M PROC 0 //SYSPRINT DD SYSOUT=* /**************************************************************/ //SYSIN DD DUMMY /* */ //* /* #IPCSTRM: IPCS ALL-PURPOSE INITIALIZATION CLIST */ //SYSUT1 DD DSN=SADUMP, /* */ // UNIT=(CART,,DEFER), /* CLIST TO END BATCH IPCS SESSION IN ORDER TO */ // LABEL=(1,NL,,EXPDT=98000), /* FREE IPCS FILES. */ // VOL=SER=00666, /* */ // LRECL=4160, /**************************************************************/ // BLKSIZE=29120, CONTROL NOFLUSH NOLIST NOMSG // RECFM=FBS, END // DISP=OLD FREE F(IPCSDDIR,IPCSPRNT) //* //JOBCARD JOB //SYSUT2 DD DSN=YOUR.SADUMP.DASD.DSN, //* // UNIT=(SYSDA,2), //*************************************************// // LRECL=4160, //*
Recommended publications

  • Administering Unidata on UNIX Platforms

    C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\ADMINUNIX\ADMINUNIXTITLE.fm March 5, 2010 1:34 pm Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta UniData Administering UniData on UNIX Platforms UDT-720-ADMU-1 C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\ADMINUNIX\ADMINUNIXTITLE.fm March 5, 2010 1:34 pm Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Notices Edition Publication date: July, 2008 Book number: UDT-720-ADMU-1 Product version: UniData 7.2 Copyright © Rocket Software, Inc. 1988-2010. All Rights Reserved. Trademarks The following trademarks appear in this publication: Trademark Trademark Owner Rocket Software™ Rocket Software, Inc. Dynamic Connect® Rocket Software, Inc. RedBack® Rocket Software, Inc. SystemBuilder™ Rocket Software, Inc. UniData® Rocket Software, Inc. UniVerse™ Rocket Software, Inc. U2™ Rocket Software, Inc. U2.NET™ Rocket Software, Inc. U2 Web Development Environment™ Rocket Software, Inc. wIntegrate® Rocket Software, Inc. Microsoft® .NET Microsoft Corporation Microsoft® Office Excel®, Outlook®, Word Microsoft Corporation Windows® Microsoft Corporation Windows® 7 Microsoft Corporation Windows Vista® Microsoft Corporation Java™ and all Java-based trademarks and logos Sun Microsystems, Inc. UNIX® X/Open Company Limited ii SB/XA Getting Started The above trademarks are property of the specified companies in the United States, other countries, or both. All other products or services mentioned in this document may be covered by the trademarks, service marks, or product names as designated by the companies who own or market them. License agreement This software and the associated documentation are proprietary and confidential to Rocket Software, Inc., are furnished under license, and may be used and copied only in accordance with the terms of such license and with the inclusion of the copyright notice.
  • Cygwin User's Guide

    Cygwin User's Guide

    Cygwin User’s Guide Cygwin User’s Guide ii Copyright © Cygwin authors Permission is granted to make and distribute verbatim copies of this documentation provided the copyright notice and this per- mission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this documentation under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this documentation into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the Free Software Foundation. Cygwin User’s Guide iii Contents 1 Cygwin Overview 1 1.1 What is it? . .1 1.2 Quick Start Guide for those more experienced with Windows . .1 1.3 Quick Start Guide for those more experienced with UNIX . .1 1.4 Are the Cygwin tools free software? . .2 1.5 A brief history of the Cygwin project . .2 1.6 Highlights of Cygwin Functionality . .3 1.6.1 Introduction . .3 1.6.2 Permissions and Security . .3 1.6.3 File Access . .3 1.6.4 Text Mode vs. Binary Mode . .4 1.6.5 ANSI C Library . .4 1.6.6 Process Creation . .5 1.6.6.1 Problems with process creation . .5 1.6.7 Signals . .6 1.6.8 Sockets . .6 1.6.9 Select . .7 1.7 What’s new and what changed in Cygwin . .7 1.7.1 What’s new and what changed in 3.2 .
  • [Linux] - Unix/Linix Commands

    [Linux] - Unix/Linix Commands

    [Linux] - Unix/Linix Commands 1. $ ssh username@servername command used to login to server 2$ pwd it prints present working directory 3$ ls -l listing the files in present directory 4$ cd..takes you to previous Dir 5$ mkdir <directory>will create directory 6$ mkdir -p /home/user1/d1/d2/d3will create all the non-existing Dir’s 7$ vi <file_name>opens file for reading/editing 8$ cat <file_name>display contents of file 9$ more <file_name>displays page by page contents of file 10$ grep <pattern> file_namechecks pattern/word in file name specified 11$ head <file_name>shows first 10 lines of file_name 12$ touch <file_name>creates a zero/dummy file 13$ ln file1 file2 creates link of file1 to file2 14$ cp <file1> <file2>Copy a file 15$ mv <file1> <file2>Move/rename a file or folder 16$ clearclears the scree 17$ whoDisplays logged in user to the system. 18$ file <file_name>shows what type of file it is like 19$wwill display more info abt the users logged in 20$ ps -efshows process 21$ which <file_name>shows if the file_name/command exists and if exists display the path 22$ rm <file_name>will delete file specified$ rm * Delete all the files in the present directory (BE CAREFUL WHILE GIVING THIS COMMAND) 23$ find . -type f -print -exec grep -i <type_ur_text_here> {} \;this is recursive grep$ find / - name <file_name> -print 24$ tail <file_name>shows last 10 lines of fileuse tail -f for continous update of file_name 25$ chmod 777 <file_name>changes file_name/directory permissions use –R switch for recursive 26$ chown owner:group <file_name>changes
  • CICS and IPCS

    CICS and IPCS

    CICS and IPCS Andre Clark Staff CICS L2 Support Agenda § Dump types § Some basic IPCS commands § CICS Verbexit DFHPDxxx § Common System Area (CSA) § Storage Manager (SM) § Transaction Manager (XM) § Dispatcher (DS) § Kernel (KE) § Loader domain (LD) § Program domain (PG) § Lock Manager (LM) § Enqueue domain (NQ) § Application domain (AP) § Task Summary (TK) § Trace (TR) 3 IPCS Primary Menu ------------------- IPCS PRIMARY OPTION MENU --------------------------------- OPTION ===> ******************** 0 DEFAULTS - Specify default dump and options * USERID - USASSC1 1 BROWSE - Browse dump data set * 2 ANALYSIS - Analyze dump contents * 3 UTILITY - Perform utility functions * TIME - 16:46 4 INVENTORY - Inventory of problem data * PREFIX - USASSC1 5 SUBMIT - Submit problem analysis job to batch * TERMINAL- 3278 6 COMMAND - Enter subcommand, CLIST or REXX exec * PF KEYS - 24 T TUTORIAL - Learn how to use the IPCS dialog ******************** X EXIT - Terminate using log and list defaults Enter END command to terminate IPCS dialog F1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=MORE F7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=CURSOR 4 IPCS Default Menu ------------------------- IPCS Default Values --------------------------------- Command ===> You may change any of the defaults listed below. The defaults shown before any changes are LOCAL. Change scope to GLOBAL to display global defaults. Scope ==> BOTH (LOCAL, GLOBAL, or BOTH) If you change the Source default, IPCS will display the current default Address Space for the new source and will ignore any data entered in the Address Space field. Source ==> DSNAME('USASSC1.SHAREFC.DUMP') Address Space ==> ASID(X'0044') Message Routing ==> NOPRINT TERMINAL Message Control ==> FLAG(WARNING) NOCONFIRM VERIFY Display Content ==> MACHINE REMARK REQUEST NOSTORAGE SYMBOL Press ENTER to update defaults.
  • Operating System Lab Manual

    Operating System Lab Manual

    OPERATING SYSTEM LAB MANUAL BASICS OF UNIX COMMANDS Ex.No:1.a INTRODUCTION TO UNIX AIM: To study about the basics of UNIX UNIX: It is a multi-user operating system. Developed at AT & T Bell Industries, USA in 1969. Ken Thomson along with Dennis Ritchie developed it from MULTICS (Multiplexed Information and Computing Service) OS. By1980, UNIX had been completely rewritten using C langua ge. LINUX: It is similar to UNIX, which is created by Linus Torualds. All UNIX commands works in Linux. Linux is a open source software. The main feature of Linux is coexisting with other OS such as windows and UNIX. STRUCTURE OF A LINUXSYSTEM: It consists of three parts. a)UNIX kernel b) Shells c) Tools and Applications UNIX KERNEL: Kernel is the core of the UNIX OS. It controls all tasks, schedule all Processes and carries out all the functions of OS. Decides when one programs tops and another starts. SHELL: Shell is the command interpreter in the UNIX OS. It accepts command from the user and analyses and interprets them 1 | P a g e BASICS OF UNIX COMMANDS Ex.No:1.b BASIC UNIX COMMANDS AIM: To study of Basic UNIX Commands and various UNIX editors such as vi, ed, ex and EMACS. CONTENT: Note: Syn->Syntax a) date –used to check the date and time Syn:$date Format Purpose Example Result +%m To display only month $date+%m 06 +%h To display month name $date+%h June +%d To display day of month $date+%d O1 +%y To display last two digits of years $date+%y 09 +%H To display hours $date+%H 10 +%M To display minutes $date+%M 45 +%S To display seconds $date+%S 55 b) cal –used to display the calendar Syn:$cal 2 2009 c)echo –used to print the message on the screen.
  • 17555: Lab: Z/OS Debugging IPCS Hands-On

    17555: Lab: Z/OS Debugging IPCS Hands-On

    1177555555:: LLaabb:: zz//OOSS DDeebbuuggggiinngg IIPPCCSS HHaannddss--oonn LLaabb WWeeddnneessddaayy,, AAuugguusstt 1122 1122::3300 PPMM JJoohhnn CC.. SShheebbeeyy IIIIII IIBBMM PPoouugghhkkeeeeppssiiee jjsshheebbeeyy@@uuss..iibbmm..ccoomm PPaattrriicciiaa LLiittttllee IIBBMM PPoouugghhkkeeeeppssiiee pplliittttllee@@uuss..iibbmm..ccoomm © 2015 IBM Corporation Lab Agenda Introduction o How the Lab is Presented …………………… 2 o Downloading Dumps via FTP ……………….. 3 o Related Sessions …………………………….. 3 o Lab Setup Instructions ……………………….. 4 Lab Exercises o Dump of Hung Job ………………………….. 5-6 o Dump of Looping Job…..…………………….. 7-8 o ABEND0C1 Dump …………………................9-11 o ABEND0C4 Dump .........................................12-14 Answers to Lab Exercises .......................... 15-25 Appendix o IPCS Option 1 - BROWSE Mode ………..…. 27 o IP ST REGS …………………………………... 28 o IP SYSTRACE ………………………………... 29 How the Lab is Presented Self-Paced o Be warned there is a lot of material in this lab. You may not finish in the time allotted. o '**' on page title indicates exercises on that page. Each exercise details commands to be entered. This lab session lets you experiment with some of the IPCS commands and displays discussed in lecture session 17907. Please refer to lecture session 17907 for sample command display output. SHARE Session 17555 2 © 2015 IBM Corporation Downloading Dumps via FTP ALL 4 data sets used in today's lab are available for FTP download. Download from TESTCASE.BOULDER.IBM.COM, login as ANONYMOUS, and use your complete E-MAIL address as the password. Files are in BINARY format in the ‘fromibm/mvs’ directory. Filenames are ‘share.s17555.dumpN.trs.bin’ (N is 1 - 4; filenames are lower case). All files are in tersed format, so will need to be untersed after download.
  • Harmonization Project Document No. 4

    Harmonization Project Document No. 4

    This report contains the collective views of an international group of experts and does not necessarily represent the decisions or the stated policy of the World Health Organization, the International Labour Organization, or the United Nations Environment Programme. Harmonization Project Document No. 4 PART 1: IPCS FRAMEWORK FOR ANALYSING THE RELEVANCE OF A CANCER MODE OF ACTION FOR HUMANS AND CASE-STUDIES PART 2: IPCS FRAMEWORK FOR ANALYSING THE RELEVANCE OF A NON-CANCER MODE OF ACTION FOR HUMANS This project was conducted within the IPCS project on the Harmonization of Approaches to the Assessment of Risk from Exposure to Chemicals. Published under the joint sponsorship of the World Health Organization, the International Labour Organization, and the United Nations Environment Programme, and produced within the framework of the Inter-Organization Programme for the Sound Management of Chemicals. The International Programme on Chemical Safety (IPCS), established in 1980, is a joint venture of the United Nations Environment Programme (UNEP), the International Labour Organization (ILO), and the World Health Organization (WHO). The overall objectives of the IPCS are to establish the scientific basis for assessment of the risk to human health and the environment from exposure to chemicals, through international peer review processes, as a prerequisite for the promotion of chemical safety, and to provide technical assistance in strengthening national capacities for the sound management of chemicals. The Inter-Organization Programme for the Sound Management of Chemicals (IOMC) was established in 1995 by UNEP, ILO, the Food and Agriculture Organization of the United Nations, WHO, the United Nations Industrial Development Organization, the United Nations Institute for Training and Research, and the Organisation for Economic Co-operation and Development (Participating Organizations), following recommendations made by the 1992 UN Conference on Environment and Development to strengthen cooperation and increase coordination in the field of chemical safety.
  • Z/OS Basic Skills Information Center: Mainframe Concepts

    Z/OS Basic Skills Information Center: Mainframe Concepts

    z/OS Basic Skills Information Center Mainframe concepts z/OS Basic Skills Information Center Mainframe concepts Note Before using this information and the product it supports, read the information in “Notices” on page 45. This edition applies to z/OS (product number 5694-A01). We appreciate your comments about this publication. Comment on specific errors or omissions, accuracy, organization, subject matter, or completeness of this book. The comments you send should pertain to only the information in this manual or product and the way in which the information is presented. For technical questions and information about products and prices, contact your IBM branch office, your IBM business partner, or your authorized remarketer. When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any way it believes appropriate without incurring any obligation to you. IBM or any other organizations will only use the personal information that you supply to contact you about the issues that you state on this form. Send your comments through this Web site: http://publib.boulder.ibm.com/infocenter/zoslnctr/v1r7/ index.jsp?topic=/com.ibm.zcontact.doc/webqs.html © Copyright International Business Machines Corporation 2005, 2008. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Introduction to the mainframe . .v Mainframe operating system: z/TPF . .22 Chapter 1. The value of the mainframe Chapter 2. Mainframe hardware today . .1 concepts . .23 The S/360: A turning point in mainframe history . .1 Mainframe hardware: Terminology . .23 Mainframe architecture: Secure, compatible, and still Mainframe hardware: Evolving design .
  • (Ipcs) User Guide Submitting Professional Medical Claims on the Medi-Cal Provider Website

    (Ipcs) User Guide Submitting Professional Medical Claims on the Medi-Cal Provider Website

    INTERNET PROFESSIONAL CLAIM SUBMISSION (IPCS) USER GUIDE SUBMITTING PROFESSIONAL MEDICAL CLAIMS ON THE MEDI-CAL PROVIDER WEBSITE July 2020 INTERNET PROFESSIONAL CLAIM SUBMISSION (IPCS) USER GUIDE Contents ABOUT THIS GUIDE .......................................................................................................................................... 1 ABOUT IPCS ................................................................................................................................................... 1 Questions................................................................................................................................................... 1 Minimum System Requirements ............................................................................................................... 2 Before You Start – IPCS Access Requirements ....................................................................................... 2 CONNECTING TO THE MEDI-CAL PROVIDER WEBSITE TO ACCESS THE IPCS APPLICATION .................................. 3 ENTERING A NEW CLAIM .................................................................................................................................. 5 IPCS Application Tips ................................................................................................................................ 5 Required Fields ......................................................................................................................................... 6 Removing Data from a Tab ......................................................................................................................
  • Z/OS Basics Preface

    Z/OS Basics Preface

    Contents Preface . iii How this course is organized . iii How each topic is organized . iv Part 1. Introduction to z/OS and the mainframe environment Chapter 1. Introduction to the new mainframe . 3 1.1 The new mainframe. 4 1.2 The S/360: A turning point in mainframe history . 4 1.3 An evolving architecture . 5 1.4 Mainframes in our midst . 6 1.5 What is a mainframe? . 7 1.6 Who uses mainframe computers?. 10 1.7 Factors contributing to mainframe use . 11 1.8 Typical mainframe workloads . 14 1.9 Roles in the mainframe world . 21 1.10 z/OS and other mainframe operating systems . 27 1.11 Summary . 29 Chapter 2. z/OS overview. 31 2.1 What is an operating system? . 32 2.2 Overview of z/OS facilities. 32 2.3 What is z/OS? . 34 2.4 Virtual storage and other mainframe concepts . 39 2.5 What is workload management? . 57 2.6 I/O and data management. 60 2.7 Supervising the execution of work in the system . 60 2.8 Defining characteristics of z/OS . 68 2.9 Licensed programs for z/OS . 69 2.10 Middleware for z/OS . 70 2.11 A brief comparison of z/OS and UNIX. 71 2.12 Summary . 73 Chapter 3. TSO/E, ISPF, and UNIX: Interactive facilities of z/OS . 75 3.1 How do we interact with z/OS? . 76 3.2 TSO overview . 76 3.3 ISPF overview . 80 3.4 z/OS UNIX interactive interfaces. 99 3.5 Summary .
  • Lecture 08: Interprocess Communication I October 21, 2019 CS631-Advancedprogrammingintheunixenvironment Slide2 System V IPC

    Lecture 08: Interprocess Communication I October 21, 2019 CS631-Advancedprogrammingintheunixenvironment Slide2 System V IPC

    CS631-AdvancedProgrammingintheUNIXEnvironment Slide1 CS631 - Advanced Programming in the UNIX Environment Interprocess Communication I Department of Computer Science Stevens Institute of Technology Jan Schaumann [email protected] https://stevens.netmeister.org/631/ Lecture 08: Interprocess Communication I October 21, 2019 CS631-AdvancedProgrammingintheUNIXEnvironment Slide2 System V IPC Three types of asynchronous IPC originating from System V: Semaphores Shared Memory Message Queues All three use IPC structures, referred to by an identifier and a key; all three are (necessarily) limited to communication between processes on one and the same host. Since these structures are not known by name, special system calls (msgget(2), semop(2), shmat(2), etc.) and special userland commands (ipcrm(1), ipcs(1), etc.) are necessary. Lecture 08: Interprocess Communication I October 21, 2019 CS631-AdvancedProgrammingintheUNIXEnvironment Slide3 System V IPC: Semaphores A semaphore is a counter used to provide access to a shared data object for multiple processes. To obtain a shared resource a process needs to do the following: 1. Test semaphore that controls the resource. 2. If value of semaphore > 0, decrement semaphore and use resource; increment semaphore when done 3. If value == 0 sleep until value > 0 Semaphores are obtained using semget(2), properties controlled using semctl(2), operations on a semaphore performed using semop(2). Lecture 08: Interprocess Communication I October 21, 2019 CS631-AdvancedProgrammingintheUNIXEnvironment Slide4
  • Avaya Session Border Controller for Enterprise 7.2 Release Notes

    Avaya Session Border Controller for Enterprise 7.2 Release Notes

    Avaya Session Border Controller for Enterprise 7.2 Release Notes Release 7.2 Issue 1 June 2017 1 © 2017 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document might be incorporated in future releases. Documentation disclaimer Avaya Inc. is not responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation to the extent made by the Customer or End User. Link disclaimer Avaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all the time and we have no control over the availability of the linked pages. Warranty Avaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya’s standard warranty language, as well as information regarding support for this product, while under warranty, is available through the Avaya Support Web site: http://support.avaya.com License USE OR INSTALLATION OF THE PRODUCT INDICATES THE END USER'S ACCEPTANCE OF THE TERMS SET FORTH HEREIN AND THE GENERAL LICENSE TERMS AVAILABLE ON THE AVAYA WEB SITE http://support.avaya.com/LicenseInfo/ ("GENERAL LICENSE TERMS").