links: コピーブランド スーパーコピー 財布 スーパーコピーブランド ブランド コピー 時計 スーパーコピー ブランドコピー激安

Structure and summary of MF topics

Contents:

Bottom

Chapter 1. List of  links to respective topics in the structure

Chapter 2. Summary   of  topics objectives in the structure

     Part 1. System programming (28 summaries)

     Part 2 . Device management

          Section 2.1. Ipl devices management  (7 summaries)

          Section 2.2. Device utilities   (2 summaries)

     Part 3. Programming applications

     Section 3.1. File transfers management (4 summaries)

     Section 3.2.  Jobs management   (2 summaries)

     Section 3.3.  VSAM management   (2 summaries)

In the  present  document    a structure  in three parts  of    all topics/articles  and  all  their  summaries are  given. To reach and view any topic/article  directly,  go to Chapter 1. List of  links to respective topics in the structure    of the Contents where you can find and press  the respective link of the chosen topic/article.

If  the wish is   to review  the summary of the article before to be opened, press the link of  word  “summary”  on the same line and you will be moved  to the corresponding  summary. After reading the summary you can return to the top of the document pressing the link of the last summary word or to press the respective  link to  open the  article.

  If   the summaries    review  of all topics/articles   is needed, go to Chapter 2. Summary   of  topics objectives in the structure of the Contents. For each part (System programming , Device management, Programming applications)  the  link  switch to the summaries  of articles in the relative  part or to the subpart sections. Pressing link of last  word in heading of  Part1, Part2, Part3, returns to the top of this document.

From every point in the document you can return to the top pressing the lighted   link of   last word of   any heading,    text/sentence.

     Chapter 1. List of  links to respective topics in the structure

The following list of topics names in the three parts  or in the subpart sections contains the links to respective topics. For each part ( System programming , Device management, Programming applications)  the  link  points  to the list of articles in the relative  part or to the subpart sections. Pressing link word Part1, Part2, Part3, returns to the top of this document.

Go to Part 1 of Chapter 1 – System programming
Go to Part 2 of Chapter 1 – Device management
Go to Part 3 of Chapter 1 – Programming application

 

System programming  Part 1

 

    1. 1.ADD OR REMOVE JES2 SPOOL VOLUME– to summary
    1. 2. CICS CEDF trace utility– to summary
    1. 3.Frequently troubles during Mainframe ZOS support– to summary
    1. 4. Mainframe Catalogs, volumes and files  management– to summary
    1. 5. Mainframe CONSOLES restore– to summary
    1. 6.Mainframe LPAR Add  or Remove – to summary
    1. 7.Mainframe z-OS support exchange data– to summary
    1. 8.Mainframe ZOS utilities– to summary
    1. 9.SCRT Report  processing  of  SMF data   for 3 LPARs– to summary
    1. 10.SMF processing– to summary
    1. 11.Stand Alone init and restore ZOS saved full DASD volumes– to summary
    1. 12.Transfer z/OS  VSAM  file via Internet– to summary
    1. 13.Troubles when Jes2 queue is  full– to summary
    1. 14.Troubles when SMF summary file is full– to summary
    1. 15.Troubles when SYSLOG or WTO buffers are full– to summary
    1. 16.Troubles with duplicated SYSID in 2 LPARs– to summary
    1. 17.Troubles with removing bad SMF records– to summary
    1. 18.Troubles with TSO Logon time delay and system wait– to summary
    1. 19.ZOS ABEND S0C7 Data exception error  in  file record– to summary
    1. 20.ZOS Logrec (Error log) processing– to summary
    1. 21.ZOS System log – SYSLOG– to summary
    1. 22.ZOS Write To Operator, Write To Operator with Reply  console messages – delete– to summary
    1. 23.Roles in Mainframe staff– to summary
    1. 24.MF terminology– to summary
    1. 25.VSAM and ZOS utilities programs– to summary
    1. 26.Mainframe Staff operations– to summary
    1. 27.Quick_ Reference  for  everyday use with z/OS– to summary
    1. 28.History of IBM Mainframe– to summary

 

 

Device management    Part 2

– Ipl devices management    – Section 2.1

Topics:

     2.1.1.   Adding new disk devices to existing Mainframe configuration– to summary

     2.1.2.  ZOS Hardware Management Console  I/O  configuration operations– to summary

     2.1.3.   ZOS IOCDS  build or change  using HCD of ISPF– to summary

     2.1.4.   ZOS IOCDS  data set  creation  using Hardware Management Console– to summary

     2.1.5.   ZOS production  IODF configuration  display create change using ISPF– to summary

     2.1.6.   ZOS test IODF configuration display/ create/ change-consoles/ add- disks using JCL source library– to summary

     2.1.7.   ZOS test IODF configuration display/ create/ change-consoles/ compare using ISPF– to summary

 

– Device utilities  Section 2.2

Topics:

     2.2.1.   Mainframe Disk utilities– to summary

     2.2.2.   Mainframe Tape utilities– to summary

 

Programming applications  – Part 3

– File transfers management   – Section 3.1

Topics:

     3.1.1. “No connection” Edit problem in TSO/ISPF C/S WSA environment  – to summary

     3.1.2. Mainframe PC communication   using  TSO C/S WSA – remarks  – to summary

     3.1.3. Mainframe Program relocation– to summary

     3.1.4. PC – Mainframe ZOS file transfer– to summary

 

– Jobs management    – Section 3.2

Topics:

     3.2.1. JES2  job   processing– to summary

     3.2.2. Print01.files  processing– to summary

 

     – VSAM management    Section 3.3

Topics:

     3.3.1. ZOS Library (PDS) utilities– to summary

     3.3.2. VSAM utilities– to summary

 

 

Chapter 2. Summary  of  topics objectives in the structure

     Part 1. System programming 

     1.1. JES2 SPOOL volumes operations – ADD OR REMOVE JES2 SPOOL VOLUME

A  procedure for display, add and remove JES2 spool volumes is described.  Displaying spool information allow  to monitor JES2 spooling and determine the action to take to control the spool environment. The current status of spool volumes and JES2  spool definitions are displayed online using  JES2 commands in TSO/ISPF environment. The same JES2 spool definitions and    parameters are fixed in the  system member SYS1.PARMLIB(JES2PARM) used during IPL of the z/OS system to create and establish the JES2 spool. A spare disk volume is used  and   initialized with prefix assigned to JES2’s spool volumes and  additional  spool space is  allocated  on it. A start spool  operator command  is issued to become the added disk volume Active in the JES2 spool.  With the  Halt and drain  spool  commands the operator  may  stop usage of  any spool  volume  (put  to inactive statusor to remove  if 0% used .

     1.2.  CICS  Execution Diagnostic Facility –  CICS CEDF trace utility

CEDF is the transaction identifier that is used to start or stop an Execution Diagnostic Facility (EDF). This facility avoids  having either CICS trace or CICS dump enabled while running CICS  application. CICS passes control to EDF at specific interception points. EDF displays the state of the application program at the interception point, and allows you to interact with EDF screens to both view additional information about the program, and overtype specific areas of the screen to test the execution of the program, before returning control to the application code.

     1.3. MF z/OS supported  troubles – Frequently troubles during Mainframe ZOS support

          1.3. 1. Duplicated SYSID in 2 LPARs during SMF processing  of   SCRT Report   for  Sub-capacity charges of Mainframe – Troubles with duplicated SYSID in 2 LPARs

          1.3. 2. TSO  Logon time delay and system wait – Troubles with TSO Logon time delay and system wait

          1.3.3. SMF summary file is  full  – Troubles when SMF summary file is full

          1.3.4. Bad SMF records when  DUMPXY  is restarted after cc=0008 – Troubles with removing bad SMF records

          1.3..5. Jes2 queue is  full – offload on tape and delete – Troubles when  Jes2 queue is  full

          1.3.6. WTO/SYSLOG  buffers are full  and   SYSLOG file  need to be saved on tape or transfered  to  PC  – Troubles when SYSLOG or WTO buffers are full        

          1.3.7. CICS online application pending in “system” –  stop, cancel, restart – item/point 7 of Frequently troubles  during Mainframe ZOS support

If the CICS online application is  pending  and all  CICS users  are   waiting in “system”, then go to  next steps     explaining how to s

top, cancel and  restart the CICS application in correct  way:

7.1. Stop CICS online application

7.2. Restart  CICS online application

7.3. VTAM generating messages stop

          1.3.8. TSO user locked – cancel (forced)  – item  8 of Frequently troubles  during Mainframe ZOS support

If TSO user is locked  (pending)  and can’t sign on (due to not logged  off  properly  with – PF3 – PF3 – PF3 – ‘Logoff’ command or  due to some operator or system error), first of all  it should be canceled (to unlock) from system operator in TSO/ISPF.

          1.3.9.  Forgotten TSO user password  – item  9  of Frequently troubles  during Mainframe ZOS support

To change or reactivate the forgotten TSO user password use alu command  as described.

          1.3.10. Forgotten CICS/KBI user password   – item   10 of Frequently troubles  during Mainframe ZOS support

To change or reassign the forgotten CICS user password follow the respective instructions.

10.1. CICS passw                          10.2. KBI password

          1.3.11.  Reactivate or add/delete  TCPIP routes required for  Mainframe   – item 11 of Frequently troubles  during Mainframe ZOS support

If TCPIP configuration is changed it is necessary   to display, update  and reactivate the  TCPIP routes to Mainframe as indicated  in the topic.

         1.3.12. Backup/Restore troubles with saved SMF file on tape – DCB parameters  – item 12 of Frequently troubles  during Mainframe ZOS support

If the  tape DCB in the restore  job   is not of an existing file  (KCI01.DMNSNTAP.MODEL.DCB), the  restore from SMF save  tape is not successful – JCL ERROR – /IEF212I RESMF02 DFDSS TAPE – DATA SET NOT FOUND/.

The solution is the tape DCB to have the same DCB used during  backup (DCB=IPOSAV.SMFDUMPW–  then   the restore from tape is   successful – cc=0000

If in  the restore  job (for saved SMF  file  on tape )   the job execution   is not successful  and

it is not possible to delete a tape volume label – go to “Case 2. The problem: RMM – error rc=12 when try to release, force any  tape”  of article Mainframe Tape utilities where this problem and the solution  are described.

          1.3.13.  No space in a Storage group to restore archive VSAM DB files  – add, delete,move VSAM files and  disk  volumes – VSAM utilities

          1.3.14. The problem “No connection” Edit/View of TSO/ISPF  library        “No connection” Edit problem in TSOISPF CS WSA environment

          1.3.15.  Logrec data set  is fullZOS Logrec (Error log) processing

     1.4.  Listing of catalog data set  names and catalog operations –  Mainframe Catalogs, volumes and files  management

In 5 cases  the basic  operations with ZOS catalogs, volumes and files   are documented: Listing  disk ALIAS, NAMES, DETAILS  and tape VGENERAL NAMES;  Printing  data sets and library members  using ISPF and batch job; Printing/display VTOC information; Building  user and tape catalogs  and operations  on them using batch job

     1.5. Repair (restore, resume) your mainframe consoles  – Mainframe CONSOLES restore

If you have Mainframe consoles as PC/3270 sessions on IBM/2074 with OS/2  System and some disaster happened (power off), all sessions go to “system” and are not working. At the same time all LPARs of Mainframe  and TSO on user terminals are still working OK. Usually in such a case when you lose your consoles, the first reaction is to turn on the power and  to do IPL of Mainframe.

But there is an easy way to repair (restore, resume) your mainframe consoles using console commands. Please follow the steps in order to achieve restoration of your lost consoles.

     1.6. Adding or removing  an LPAR to existing Mainframe configuration  –  Mainframe LPAR   Add  or Remove

The present topic describes the technology for adding or removing  an LPAR to existing Mainframe configuration with its base configuration components – CPU, disks storage, tapes storage, consoles,  ESCON channels, TCP/IP and Ethernet  connections. IOCDS resources  are added/removed  for the  new LPAR  and IODF definitions  for them are corrected in the similar way. To prepare IPL for  the new LPAR   all the necessary system data sets and system volumes have to be prepared and new IPL and IODF parameters volumes added. HMC definitions, changes and operations are necessary to be performed before new IPL. Profile definitions & changes should be performed in the consoles server for the emulated new consoles of this LPAR.  TCPIP profile definitions & changes  are necessary to be done in the z/OS system facilities of the LPAR to permit access to it from any TSO users on local or remote terminals. To be all the LPAR’s  balanced against MIPS and MSU of the Mainframe some actions in HMC should be performed.

     1.7. Exchange data with Mainframe support  –  Mainframe z-OS support  exchange data

To have  a qualified  IBM Mainframe support  of z/OS   sometimes you are required to send system/application   data  concerning the problems of  z/OS    processing functions or applications.

If you need a Mainframe support utility   programs   (for problems as  SCRT report not accepted from IBM/LMS because one of the  LPAR’s  in one  CPU of Mainframe has duplicated SYSID with another LPAR  on the same CPU or if the  bad SMF records has  to be  removed before SCRT processing), go to  item 1 of the Contents.

If you are advised  to send  z/OS  system  documentation because   the  TSO  customers are waiting too much when logging on  in only one particular LPAR of the CPU and on other LPAR’s no time delay exists with  TSO logon, go to item 2 of the Contents.

When you are required to send  Logrec data for analysis of some problem  from IBM z/OS support, go to item 3 of the Contents.

When you are required  to send  Syslog  data for analysis of some problem  from IBM  z/OS support, go to item 4 of the Contents.

     1.8.  Utilities for files, Vtoc and disk dump –  Mainframe ZOS utilities

The following 5 examples of frequently   occurring utility cases  with Mainframe in z/os are documented. When   you need to process   a file that is busy, it is important to find out who is using the file.  An easy way exists   to receive   VTOC information – batch printing with IEHLIST   or to view  online VTOC using Ditto.  There is a way to have batch VTOC listing through Ditto.  Dump/restore   of full disk volumes  can be performed  to/from  tape.

     1.9. Monthly Report  processing  of  SMF data   for 3 LPARs –  SCRT  Report  processing  of  SMF data   for 3 LPARs

SCRT  monthly Report  processing  of  SMF data   for 3 LPARs of Mainframe  including SMF dump jobs  and link to  IBM/LMS  are  described below. For each LPAR the summary  SMF file is copied  after  the 01 day of the current  month on a save file, the current summary file is emptied  to continue collecting the  SMF data and   extract of SMF  records TYPE(70,89) from saved SMF files for the reporting period from 02 day of previous month  to 01 day of current month  inclusive are  performed   on a  disk volume  common for all 3 LPAR’s.  Next  a new  common extract  is performed  for   SMF  records TYPE(70,89) using  the 3 LPAR extracts and the common extract is used as  input to produce the final common SCRT report for the whole  Mainframe in library member HLQ.SCRTTOOL.CSV(#836093F). The library member file #836093F is transfered  from  the common disk volume of MF to  PC in character format   as file  ready to be submitted  to  the IBM/LMS  application link between the 2nd and the 9th day of the month inclusive.  After successfully submitting  the SCRT report  a  Confirmation Report  from IBM/LMS  is received for the applied  minimized  Software Charges of  the reporting period.

The final operations include backup on a separate save SMF  tape  for each LPAR the   previous  SMF summary files, deletion  the  old ones and restore from tape if necessary.

     1.10. Minimizing  the   monthly software charges on the base of real usage of Mainframe resources SMF processing

SMF (System Management Facilities) collects and records system and job-related information that your installation can use in:
• Billing users.
• Reporting reliability.
• Analyzing the configuration.
• Scheduling jobs.
• Summarizing direct access volume activity.
• Evaluating data set activity.
• Profiling system resource use.
• Maintaining system security.
SMF formats the information that it gathers into system-related records (or job-related records). System-related SMF records include information about the configuration, paging activity, and workload. Job-related records include information on the CPU time, SYSOUT activity, and data set activity of each job step, job, APPC/MVS transaction program, and TSO/E session.

When you are running z/OS in 64-bit mode and are no longer running OS/390 on your System z server, you have the option to pay the charges for your eligible software on a sub-capacity basis. The Sub-Capacity Reporting Tool (SCRT) is the program which processes SMF 70 and SMF 89 records created by z/OS to produce a report showing LPAR utilization figures which are used to set the software charges. Sub-capacity pricing is based on the four-hour rolling average utilization of the z/OS LPARs observed within a one month reporting period. The reporting periods run from 00:00 on the second calendar day of the month through midnight (23:59) on the first calendar day of the following month.

     1.11. Backup  on tape  z/OS system volumes to be restored in Stand Alone environment Stand Alone init and restore  ZOS  saved  full  DASD volumes

 

When the  IPL or other system  DASD  volume of z/OS is destroyed or damaged and it is not possible to IPL z/OS system,  you need a procedure for full volume backups (on tape) of system volumes to be restored in Stand Alone environment. Here the Creation of two Stand  Alone IPL tapes is described – one to initialize any  DASD volume and other  – to restore DASD volume from DFSMSdss backup tape. The process of Stand Alone  initializing  and restoring  is  shown in detail with working examples. If you have an available running z/OS system you can  restore from full DASD tape copy any damaged  or changed disk volume when necessary.

 

     1.12.  Transfer  z/OS VSAM file (ESDS or KSDS)  from  one local  Mainframe to another remote Mainframe  using E-mail medium of Internet  –  Transfer  z/OS  VSAM  file via Internet

 

To transfer  z/OS VSAM file (ESDS or KSDS)  from one local  Mainframe to another remote Mainframe a procedure using E-mail medium of Internet is described. Sometimes VSAM files occupy  a large space on Mainframe  and file size should be minimized to be transferred via E- mail. The examples below show VSAM  ESDS  file minimized 20 times and KSDS minimized 33 times before sending and receiving via Internet. The sequence of steps convert VSAM file (ESDS or KSDS) to z/OS sequential file (DSORG=PS), condense the  z/OS sequential file before  download  as binary file to local  PC where the file is Zipped,  attached to e-mail  and sent to another  remote PC user. When received on PC at the remote location, the binary file is unZipped, uploaded  to Mainframe as binary file, uncondensed as z/OS sequential file  and converted to respective VSAM (ESDA or KSDS) file. The REPRO command is used to  retrieve  records  from  a  sequential or VSAM  data   set and  store  them in VSAM format in a key-sequenced, entry-sequenced or a sequential data set. When records are to be stored in key sequence, index entries are created and loaded into an index component as data control intervals and control areas are filled.  Free space is left as indicated in the cluster definition in the catalog. A minimum set of DCB parameters should be included in the respective DD statements with appropriate volume and unit parameters in the job examples.

     1.13. JES2 queue is full  –  Troubles when  Jes2 queue is  full

If  a message appears  that JES2 queue is full  and nobody can logon in TSO,  then some Emergency   actions should be performed to reanimate  the system. If a warning message  appears that JES2 limit is reached,  some actions are necessary to avoid the status of JES2 full.    In the all cases above  go to item 1 (Emergency   actions if warning  limit reached or  full   JES2) of the Contents.

If  you have a care about the JES2 queue properly  processing and maintenance (not to be 100% full when stops  z/OS functioning),  go to item 2 (JES2     offload on tape and delete) of the Contents.

     1.14. SMF summary file is   full Troubles when SMF summary file is   full

When SMF summary file is   full and  the job DUMPXY of z/   ended  with cc=0008 (due to 100% full of  SMF summary file)   and a new active work SMF file  is switched with   dump  required  it is necessary to perform some emergency actions to solve the problem  and  to avoid this situation in the future.  A warning message is received that SMF summary file is 100% full, the normal process of  gathering  SMF records via DUMPXY on the current active work SMF file  (S-BC2A.MAN2) and writing (dump ) it on the SMF summary file  (when 99% filled up)   is interrupted.  The job DUMPXY  is  ended  with cc=0008 requiring a dump of the current active work file (99% filled up)  to be performed because   SMF summary file is full. The next  alternate work  file (P-BC2A.MAN1) is started as active  to continue gathering next  SMF data without loss of SMF records.T he system requires dump to be performed from the work file S-BC2A.MAN2  (99% FULL)    to  the SMF summary file. The first thing to do  is to save the present status of the  full   SMF summary file  IPOSAV.SMFDUMPW  (if it is  necessary for further processing) on  saved  file KCI08.SMF.D221112 .

     1.15. SYSLOG or WTO buffers are full  –  Troubles when SYSLOG or WTO buffers are full

When  SYSLOG or WTO buffers are full and   SYSLOG file  need to be saved on tape or  transfered  to  PC,   some action described below  have  to be performed.

When  WTO/R or SYSLOG buffers reached their  limits  or are  full,  it is necessary to investigate the buffer limits with the TSO/ISPF sd.log command ‘D C,HC’ and compare them  with the limits  in the normal system status. Go to item 1 of Contents.

To save the current  SYSLOG data on tape a  procedure is used for daily/monthly processing of SYSLOG  on a production system , minimizing  the size of the  SYSLOG. Go to item 2 of Contents.

To save the current SYSLOG STC****  to PC for later  investigating and analysis,  z/OS  file is created  that contains all SYSLOG current data  and sent to PC with MF-PC text file transfer. Go to item 3 of Contents.

     1.16.  Renaming  the SMF input  records with duplicated SYSID (BC2A)   for   LPAR BC3A  –Troubles with duplicated SYSID in 2 LPARs

During the  process of SCRT Sub-capacity report for charges of Mainframe processing  a problem arises when 2 LPARs (BC2A and BC3A)   have  the same   SYSID (BC2A) (the duplicated LPAR BC3A is a full copy   of the same z/OS system  in  the first  LPAR BC2A with its   own disk volumes   adjusted for its  IPL  and the new disk storage devices). The two  z/OS systems are working OK on different LPARs having  the same disk volume names on different disk device addresses  and with  different TCP IP addresses. Care is taken in the common  IOCDS and in the different COMMND00 members of respective  library sys1.parmlib   the  disk addresses in each LPAR to be unique online or set in their IODFs online or offline respectively.

To  have the same  SYSID name running on the same  Mainframe  in two  LPARs   is not a trouble for the two independed systems.  Concerning the  SCRT Support however – the Duplicate SYSIDs is a restriction of SCRT –  this is a trouble  problem!  The  SCRT program requires combined SMF  information for all  3 activated LPARs.

The solution in  this case is to   rename  the SMF input  records with duplicated SYSID (BC2A)   for   LPAR BC3A  as SYSID (BC3A) using the   utility program PATTRSNW .

     1.17. Removing bad SMF records  Troubles with removing bad SMF records

When the failed job  DUMPXY with RC=0008 is resubmitted the following  trouble can occur – some SMF records  are dumped (written) in a wrong way  on the summary SMF file (IPOSAV.SMFDUMPW) that will reflect negative on the monthly SCRT report processing  for Sub-capacity charges of Mainframe. The bad SMF records are  detected   and  removed.

When an SMF extract from KCI08.SMF.D051112 (copy of   IPOSAV.SMFDUMPW  after resubmitting job  DUMPXY with RC=0008)  is read, an ABEND002 with rc=0004 occurs during writing the SMF records to the output file HLQ.SMFEXTR.FEB90.

When  more records are modified  to the end of the dataset, the partial  record is then followed by valid records.  Since SMF records can   span blocks, the segment descriptor word (SDW) is used to determine if    a record is complete; the 1st part of a segmented record, the  middle part of a segmented record, or the end of a segmented  record. When  another record is modified onto the partial record, the segment    descriptor words may not match up.

The solution of this problem (Abend002-04) is to use the program  VBSFIX    designed to read a VBS (non-VSAM)    data set and check on valid SDW‘s. Invalid segments are converted to VB output in file ‘BADRECS’. Valid records are copied to file ‘OUTPUT’.

     1.18. TSO logon time delay  or system wait  –  Troubles with TSO Logon time delay and system wait

If you  or other customers are waiting too much when logging on  TSO of z/OS in only one particular LPAR of the CPU and no TSO logon time delay exists  on   other LPAR’s, go to item 1 of the Contents. If TSO is in   system wait  troubles during normal operations, go to  item  2  of the Contents.

     1.19.  Data exception interruption  with dump analysis for  Cobol  program executionZOS ABEND S0C7  Data exception error  in  file record

Investigation of ZOS system error ABEND S0C7 due to error data in a file record that caused  data exception interruption of program instruction to occur  is made. Dump analysis with Cobol source program compiled and executed are performed on the base of PSW information, Assembler listing of Cobol compilation and  dump investigation. Detected is  the right record and the exact error field in the file. The error field  is     repared  and the program execution is restarted with successful end.   A  similar  approach is applied to dump analysis for  Cobol  program execution without source available for error field record detecting in  two different files with   finding  out the exact file from the dump. The same technology may be used  and developed for any program interruptions  of other  ZOS application programs.

     1.20. Prevention  the stop of   error recording   –  ZOS Logrec (Error log)  processing

The error system  records (collected information about hardware and software errors in the form of an error log) are  placed in the error recording data set (ERDS also known  as LOGREC – logrec data set) by the Error Recovery Program (ERP) of the  z/OS operating system. This error log may be written to a z/OS unique  ‘dataset’  or  in a sysplex – to a ‘logstream’, or you may decide not to record the error log. If the ERDS/LOGREC  fills up, then recording stops, and Z/OS continues with no error log recording.

To prevent the stop of   error recording,   the log is  offloaded to a history dataset, which is used to make tape back-ups at regular intervals, LOGREC is cleared for new use and  the reports are printed  for  analyzes.

     1.21. SYSLOG processingZOS System log –  SYSLOG

The system log (SYSLOG) is a data set  residing in the primary job entry subsystem’s spool space. This is SPOOL data, not a data set that can be accessed in any normal way and  there is no data set name assigned to a spool file.  It can be used by application and system programmers (through the WTL macro)  to record communications about problem programs and system functions.

     1.22. Removing Information from console operator Screen  –  ZOS Write To Operator,   Write To Operator with Reply  console messages – delete

Sometimes  the  ZOS console operator message area occurs to be  full and the generation  of messages (WTO, WTOR)  from the system  is stopped. The system is not usable  and need urgent system actions.Use the CONTROL E command to remove various types of messages from the screen or to cause message numbers to be deleted.

     1.23. Roles in Mainframe staff  Roles in Mainframe staff

Mainframe systems are designed to be used by large numbers of people /users/ who interact with the applications that are hosted on the system and run in batch or online environment. The sophistication and complexity of the system software that supports the users and applications require different  roles of the  staff  to operate and support the mainframe system.

      1.24. MF terminology  – MF terminology

The most often abbreviations  and  concepts of  IBM Mainframe  software  and  hardware documentation are  given in alphabetical  sequence.

     1.25. VSAM  and z/OS utilities programs   –      VSAM  and ZOS utilities programs

To get more information about  useful files,  JCL of working programs and documents used in the topics/documents of this Handbook reference look at this aggregation of VSAM  and z/OS utilities programs.

     1.26.  Mainframe Staff operations –  Mainframe Staff operations

This is a sample CHECK LIST for production  LPAR BC2A/90 IPL procedure of  bank  IBM Mainframe with z/OS. Staff operations duties are to start and stop MF in Machine room following   the check list prescription.

     1.27. Quick_ Reference  for  everyday use with z/OS  –  Quick_ Reference  for  everyday use with z/OS

The present reference is an aggregation of  system commands and  activities during a bank IBM Mainframe support:

        1. Any mixed accidental operation commands
        2. TSO/ISPF System commands
        3. “No connection” problem in TSO/ISPF C/S wsa environment
        4. Add a new KBI/Dimension user in CICS10/90
        5. TSO/ISPF other specific operations
        6. TSO/ISPF da
        7. Logrec operations (ERP clearing)
        8. JES2 – clearing
        9. Print01 – clearing
        10. SMF – clear
        11. Console messages processing (clear)
        12. SYSLOG processing (clearing)
        13. LPAR system name – sys1.parmlib(IEASYS00) – sysname=bc2a system name
        14. BC2A DUMPs – delete
        15. 15. Map a letter Y to directory access
        16. /D IKJTSO,SEND
        17. RMF Monitor III options in ERBRMF04 of sys1.parmlib

      1. Monitor III report commands – Overview

    >

         1.28.    History of IBM Mainframe        –                    History of IBM Mainframe

    The history of IBM Mainframe development is described in short.

    The main points of hardware  and software developments are defined   during the years up to 2014.

         Part 2 . Device management  

         Section 2.1. Ipl devices management

              2.1.1. Add new  disk devices  to IOCDS  configuration (by  HCD or HMC technology)  using the updated IODF    –  Adding new disk devices to existing Mainframe configuration

    An easy way how to add   new   formatted   LCU (logical control unit)) and newly created Device addresses   to  existing  Mainframe  configuration (if a ESS800 shark storage is available)   is described below. The first step is to update and create  IODF  work configuration with the added  LCU and newly created Devices   followed by IODF  building  (using HCD or JCL technology). The next step is to build the new IOCDS configuration (by  HCD or HMC technology)  using the updated IODF  work configuration followed by IPL prepare before starting the modified system configuration. The  new IOCDS is used at POR (Power Off Reset) time  before IPL to make the new configuration data known to z/OS.

              2.1.2.  HMC operations for the choosen  I/O configuration (IOCDS)ZOS Hardware Management Console  I/O  configuration operations

    Here some usefull HMC /Hardware Management Console/  ZOS  I/O Mainframe configuration operations on OS 2 WARP  of  IBM  NetVista/ Pentium 4 are described. First of all you have to Sign on OS 2 WARP. Then go to  Start  IBM Primary Support Element and from TASK LIST of operations choose  the CPC Configuration. If you wish  to see which  I/O Configuration  (IOCDS A0) is active,  go to I/O Configuration function (A0/new (last created on 16.01.2010) – A3/old/+VSE/LPAR  + D0/Diagnose configurations are listed) – you will see that A0  from 16.01.2010 is active.  To operate with any  I/O configuration (IOCDS),  position the desired configuration and  process within  the TASK LIST. Different  function options exist for the choosen  I/O configuration (IOCDS).

    You may write a new A0 configuration generated by HMC or TSO/JES JOB if  “Disable write protection “ function option for  the new configuration is activated. To view or edit the active  A0 configuration you have to “Disable write protection”, “Disassemble data set” and then “Open source file”.

    Very short rules are given for starting  and stoping  Mainframe when urgent actions are needed.

              2.1.3. Build the new IOCDS  by  HCD  technology  using the new  production  IODF  configuration  –  ZOS IOCDS  build or change  using HCD of ISPF

    If you have to build an IOCDS  (Input Output Control Data Set)  using a new created production  IODF (Input Output Definition File)  configuration file an  easy way exists with  the  HCD /Hardware Configuration Definition/ function of TSO/ISPF.  This new IOCDS is used at POR (Power Off Reset) time to make the new configuration data known to z/OS.  After entering HC of ISPF menu you have to specify the name of the I/O definition file . . . ( ‘SYS1.IODF48’ )     to be used and continue with Build IOCDS function. Then you have to perform some  Actions on selected IOCDS configuration(A0, A1, A2..) –   Update IOCDS and  writing/rename  the title  and date of the changed configuration.  A  job is generated “CRIOCDS  JOB07466 “  that is  submitted,  but not started. On syslog (sd.log) you have to answer/ REPLY     ‘YES’  for  the  job  “CRIOCDS”  to WRITE TO LEVEL A0 IOCDS or A1 IOCDS which  is choosen  to be replaced (“Disable write protection” for this  IOCDS  must be activated from HMC/Hardware Management Console/).

              2.1.4. Build the new IOCDS  by  HMC  technology  using the new  IODF  configuration –   ZOS IOCDS  data set  creation  using Hardware Management Console

    If you want  to build IOCDS (Input Output Configuration Data Set)   by HMC (Hardware Management Console) first of all you have to Sign in OS 2 WARP. Then go to  Start  IBM Primary Support Element  by pressing Single object operations from CPC Configuration  option  in  TASK LIST of operations. If you wish  to see which  I/O Configuration  (IOCDS A0) is active,  go to I/O Configuration function (A0/new(last created on 16.01.2010) – A3/old/+VSE/LPAR  + D0/Diagnose configurations are listed) – then you will see that A0  from 16.01.2010 is active.  To operate with any  I/O configuration (IOCDS),  position the desired configuration and  process within  the TASK LIST. Different  function options exist for the choosen  I/O configuration (IOCDS).  You may write a new A0 configuration generated by HMC only if  “Disable write protection “ function option for  the selected  configuration is activated.

    To create a  new A0 configuration from I/O Configuration file ZB_1001 for  A0/new(16.01.2010-without VSE LPAR) prepared on diskette,  you have to put the diskette on the diskette  drive of HMC/PC IBM  NetVista/ Pentium 4 and copy the configuration as A0. To view or edit the active  A0 configuration you have to “Disable write protection”, to “Disassemble data set”,  then “Open source file”  and and save it.  Enter “Build data”  function to create  IOCDS  as A0 and exit to finish operations.

              2.1.5. Display, update and create  new production IODF using HCDZOS production  IODF configuration  display create change using ISPF

    The  4 examples bellow  of frequently  occurring cases  with production  IODF (Input Output Definition File) configuration of LPAR  using HCD (Hardware Configuration Definition) of TSO/ISPF are concerning the production LPAR BC2A of IBM/ZOS. The  descriptions  of the  cases bellow  explain how to: display  the old  work configuration IODF38, create a new IODF39 (by copy of old one), change device parameters and  delete (if IODF is wrong and require to create another) are followed by production IODF39  building  and   IPL prepare (to copy the old LOAD38 and to create new member SYS1.IPLPARM(LOAD39). The changes refer to disk volume  addresses  163A, … changing the Device Definition  parameter OFFLINE from YES to NO (or from NO to YES), so that the device 163A after IPL of  LPAR BC2A to be in the desired status – offline or online. This is necessary if two or more LPARs have access to all (common)  disk volume addresses  with duplicated volume names  in one environment and they should be separated.

              2.1.6. Display, change  and create  new test  IODF using JCL source library  –   ZOS test  IODF configuration  display create change-consoles add- disks  using JCL source library

    These 7 examples of frequently  occurring cases  with test  IODF (Input Output Definition File) configuration using JCL source ZOS  library KCI88.ZOS140.BASE.LIB are concerning the test  LPAR BC3A. The  descriptions  of the  cases bellow  explain how to: display  the  old  jcl   source KCI88.ZOS140.BASE.LIB (IODF2B and MVSIO2B), create   new IODF42 and MVSIO42 jcl   source definitions (by copy the  IODF2B and MVSIIO2B old members), change device parameters of  IODEVCE UNIT statement in MVSIO042 member,   followed by building  the production IODF42 configuration   after  IODF42 jcl execution and   IPL prepare (to copy the old LOAD2B and to  create a new member SYS1.IPLPARM(LOAD42). The changes refer disk volume  addresses  163A, … changing the IODEVCE UNIT statement  parameter from default (which is OFFLINE=NO – meaning online of 163A) to OFFLINE=YES (meaning offline of 163A), so that the device 163A at  IPL of  LPAR BC2A to be in the desired status – offline. This is necessary if two or more LPARs have access to all disk volume addresses  with duplicated volume names  in one environment and they should be separated. Another changes refer to consoles addresses 0D00,16 omitting for them the parameter of LPAR BC2A in statement  IODEVICE ADDRESS,  so that partition name definition  is omitted and during IPL these addresses are not dependent of LPAR name.

              2.1.7. Display, change  and create  new test  IODF using ISPF  –  ZOS test IODF configuration display/ create/ change-consoles/ compare using ISPF

    These  5 examples of frequently  occurring cases  with test  IODF (Input Output Definition File)  configuration of LPAR  using HCD (Hardware Configuration Definition)  of TSO/ISPF are concerning the test  LPAR BC3A. The  descriptions  of the  cases bellow  explain how to: display  the old  work configuration IODF38,  create new IODF48 (by copy of old one), change device /consoles/  parameters and  delete (if IODF is wrong and require to create another) are followed by production IODF48  building,  IPL prepare (to copy the old LOAD2B and to create new member SYS1.IPLPARM(LOAD48) and  to compare  the old and the new configuration are they changed. The changes refer consoles addresses 0D00,16 excluded from the explicit device candidate list for LPAR BC2A, so that partition name description is omitted and during IPL these
    addresses are not dependen
    from LPAR name.

         Section 2.2.
    utilities

              2.2.1. Processing disk devices of  z/OSMainframe Disk utilities

    Here are pointed   some interactive storage operations  of  z/OS Interactive Storage Management Facility (ISPF) showing  how  to add  new/additional   disk   volumes    with:  the necessary storage parameters (DCEXT for big files),  to perform  functions against Data Sets and  Volumes , to specify Data Set and system names,  to execute ACS  (Automatic Class Selection) Routines and Test Criteria.  Details are given how to remove disk  volume from one  storage group and add to another including  the actions for defining/deleting user catalog and alias (file prefixes) on the new disk volumes . The process of search and find spare disk volumes  and the following  special initialization for storage group  usage and  vvds definitions are also described in details. When a new storage group is necessary,  first  you have  to add  it  to  DFSMS and then  create   the new  group contents. The support include actions for delete/remove volume from storage group and how to change the disk volume number on which is  the catalog in  the storage group.

              2.2.2. Processing tape  devices of  z/OS  – Mainframe Tape utilities

    Six cases showing  how to solve tape problems using standard tape utilities under DFSMSrmm. What to do if it is not possible to release a tape  name and  to add the same  name with different parameters! How to add a scratch tape and how to initialize it to be usable in production time. If you have tapes with different VTOC volume name prefixes  not existing in the system  –  how to add them  in DFSMSrmm system . Using “ditto” functions  to see everything on
    tape volume.

         Part 3. Programming/a> applications

         Section 3.1. File transfers management

              3.1.1. The problem “No connection” Edit/View of TSO/ISPF  library“No connection” Edit problem in TSO/ISPF C/S WSA environment

    The following “No connection”  problem may arise during or after finishing your client/server connection  with  ISPF C/S WSA for file transfers as follows.

    If you are working in ISPF C/S WSA for file transfers between PC and Mainframe and when finally you  exit from this connection with WSDISCON command in ISPF or stop wsa.exe application on PC,   a nagging message in TSO ‘No Connection’  appears when you want to edit/view  any member in edit /view  mode  of  ISPF library.

    One of ISPF’s “best kept secrets” in z/OS is the Work Station Agent (WSA for short). When you have not enough z/OS experience or you have by chance not properly operated with TSO/ISPF C/S WSA complicated functionality you may get into situation not  able to do your everyday system work as result of some remained  settings.

              3.1.2.  Remarks concerning  TSO C/S WSA  communicationMainframe PC communication   using  TSO C/S WSA – remarks

    Nevertheless of all beauties of  IBM TSO C/S WSA  in z/OS it is honestly to make the following remarks:

              Remark 1. Complicated operations compared to IND$FILE or FTP file transfer

              Remark 2. The function “Upload of full library”  doesn’t exist

              Remark 3. TSO split screens are not possible

              Remark 4. WSA (PC-client) session has  short delay time

              Remark 5.  Download/upload of load library member in text mode

              3.1.3.  Moving Source, Object and Load  z/OS  programs to another  Mainframe –  Mainframe Program relocation

    Sometimes it’s necessary to move some programs and data  from one place to  another  (as is the case with program distribution  or exchange  among the program developers in one team)  on the same z/OS Mainframe in different formats – source, object or load.  When the relocation requires the programs and data  to be transferred to another  remote  Mainframe,   the process may be extended with inclusion  Internet and  removable portable media (CD, DVD, tape cartridge).

    Case 1.  Source program relocation

    Case 2.  Object  module relocation

    Case 3.  Load  program relocation

              3.1.4. PC to Mainframe  file communication –  PC –  Mainframe ZOS file transfer

    These are 14 practical examples of frequently occurring cases with z/OS – PC file transfer. Prerequisite is IBM PC 3270 terminal emulator installed on PC/Windows with Telnet PC 3270 terminal session (or equivalent) started and TCP/IP connection to Mainframe IBM z/OS.

         Case1. How to get JES2 job execution output data to PC/Microsoft folder
    (using GET function of FTP/PC and automatic logon to TSO ISPF)

         Case2. How to send Print01 z/OS file data to PC TCP/IP FTP server
    (using PUT function of FTP z/OS in job FTPRINT)

         Case3. How to receive Print01 z/OS file data on PC folder in character/binary format
    (using Command Prompt of WINDOWS and IND$FILE GET TSO ISPF function with P.6
    menue active in a: Telnet session)

         Case4. How to send a file from PC to Print01 z/OS file data in character/binary format
    (using Command Prompt of WINDOWS and IND$FILE PUT TSO ISPF function with P.6
    menue active in a: Telnet session)

         Case5. How to download z/OS source library member to PC in character/binary format
    (using IND$FILE GET TSO ISPF function via dropdown Actions menu of P.6 menue active)

         Case6. How to upload a file from PC to z/OS source library (in character/binary format)
    (using IND$FILE PUT TSO ISPF function via dropdown Actions menu of P.6 menue active)

         Case7. How to receive z/OS source library member to PC folder in character/binary format
    (using Command Prompt of WINDOWS and IND$FILE GET TSO ISPF function with P.6
    menue active in a: Telnet session)

         Case8. How to send a file from PC to z/OS source library in character/binary format
    (using Command Prompt of WINDOWS and IND$FILE PUT TSO ISPF function with P.6
    menue active in a: Telnet session)

          Case9. How to receive z/OS load/object library member to PC folder in binary format
    (using Command Prompt of WINDOWS and IND$FILE GET TSO ISPF function with P.6
    menue active in a: Telnet session)

        Case10. How to send a file from PC to z/OS load/object library in binary format
    (using Command Prompt of WINDOWS and IND$FILE PUT TSO ISPF function with P.6
    menue active in a: Telnet session)

         Case11. How to get z/OS source/load library member to PC in character/binary format
    (using FTP TCP/IP sign on TSO in Command Prompt of WINDOWS and get command)

         Case12. How to put a file from PC to z/OS source/load library in character/binary format
    (using FTP TCP/IP sign on TSO in Command Prompt of WINDOWS and put command)

         Case13. How to get full z/OS source/load/object library from MF to PC in character/binary
    (using FTP TCP/IP sign on TSO in Command Prompt of WINDOWS and mget command)

         Case14. How to put full z/OS source/load/object library from PC to MF in character/binary
    (using FTP TCP/IP sign on TSO in Command Prompt of WINDOWS and mput command)

         Section 3.2.  Jobs management

              3.2.1. JES2 job and data processing –  JES2  job   processing

    JES2 Spool data set consists of   SYSOUT + JCL source + SYSIN data + JCL contol blocks. JES2 analyze and groups job outputs for output class,route code,priority, Etc.

    If we  are referring to the JES2 output of a single job — this is SPOOL data, not a data set that can be accessed in any normal way. There is no data set name assigned to a spool file.

    – View and save JES2 job data on a MVS file

    – Useful JES2 commands

    – BACKUP/OFFLOAD  of   JES2 – Q to tape

    RESTORE/RELOAD  from  JES-Q TAPE

              3.2.2. Creating  and processing Printo1 files –  Print01.files  processing

    Print01 z/os  file ’print01.restroz’  created from JES2 queue  using print function  of  TSO ISPF for  sending later via FTP  to PC.

    Intermediate file PRINT01.SMFEXTR.FEB  produced by SMFEXTRA tool  of Sub-Capacity for z/OS to  minimize charges SMFEXTRA and to be processed by the next job SCPTOOL that calc- ulate  the extract of smf data  creating  print01.scptool.csv report.

    – Intermediate file PRINT01.KCI02.B6600.HDESK.HISGLACC.G10 cteated by PGM=GLVKALL (banking GL inquiry)  to be sent to PC via FTP.

    – Any Cobol program can produce Print01  sequential file (PRTFILE)

                   2.1. Daily backup of Print01.files and delete

    2.2. Saved summary backup  on TAPE

    2.3. Restore a report from saved backup tape

     

         Section 3.3.  VSAM management

              3.3.1. Processing libraries in z/OS –  ZOS Library (PDS) utilities

     

    Partitioned data sets (PDS) are libraries that contain files called members. There are two kinds of partitioned data sets. One can contain source code, macros, cataloged procedures and other data. The other, called a load library, can contain only load modules.

    Examples of frequently   occurring cases  with z/os library in Mainframe are described. Sometimes it’s easyer to create a library with batch job,   another time this may be done online using TSO/ISPF. In some cases it is necessary to rename the library while you are in   TSO/ISPF. A  job  sequence is shown how to expand PDS library batch changing  the space units. If new library definition  (with special  prefix KCI88) should  be added in DFHSMS (Storage Management System), some changes are necessary to be done in members scprod01 and sgprod01 of Bc2a.zos140.dfsms.acs library.   After a high volume of activity  with Library (PDS)  there are  unusable gaps or spaces within the PDS  that require a  compress function using IEBCOPY to compress the members and consolidate all the gaps or spaces – some approaches are file.

              3.3.2.  Backup, restore disk and files in VSAM storage –   VSAM utilities

    If you need a space to restore archive VSAM DB files on existing storage group  without adding new disk volumes,          the  deleting  unused VSAM files and  initializing volumes  with the obsolete data is shown in   article     followed by  move/condense VSAM files   to freed disk space on volumes.

    In the following 9 examples some frequently occurring cases with z/os VSAM in Mainframe are documented. Relocation VSAM files to obtain more free disk volumes, copy of disks and files from one storage group to another are described. Backup/restore of VSAM files and PDS /libraries/ to/from tape, repro VSAM file to save old contents and rename VSAM files in the same catalog are also shown. Export/Import VSAM files using output/input tapes or output/input disk files between two different systems (z/os and VSE) in one environment are very usefull and are used often in practice . GL management – restore GL -files , processing and routing them to local PC server is one convenient way to route VSAM application data to PC . Mass delete VSAM files, delete/purge VSAM cluster files and delete garbage (non VSAM, VVR and NVR files) are the procedures that keep the VSAM space always clean and at minimum usable size.

    end

Choose donation amount:

Leave A Reply

Comments

No comments yet, be the first to add one!

Places

 

Choose donation amount:
您要找的资源已被删除、已更名或暂时不可用。 Clef two-factor authentication