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

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.

 

CONTENTS

Bottom

1. Receive  z/OS support utility  programs prepared on remote  Mainframe

           1.1. Receive SYSID renaming  executable  z/OS program module via IBM support e-mail  

           1.2. Receive  new   Version of SCRT executable module from IBM LMS  WEB site

           1.3. Receive source  program VBSFIX to remove bad SMF records via IBM support  e-mail

           1.4. ReceiveTRSMAIN utility program to compress data exchanged using  IBM support WEB site

2. Send Logon TSO time delay exchange data

           2.1. Send job list of Cobol job execution

          2.2. Send SVC dump  condense data

          2.3. Send monitoring condense data

3. Send Logrec data 

4. Send SYSLOG data

 

 

          1. Receive z/OS support utility programs prepared on remote  Mainframe

                    1.1. Receive  SYSID renaming   executable  z/OS program module via e-mail

To receive and use  a binary file comprising JCL and executable (load)   program  ready for execution included  after      PGM=LOADER statement (//    EXEC PGM=LOADER,PARM=’/BC2A*BC3A’) with  some parameters adjustements to the  local configuration, follow the next description.

The binary file  rensysio.bin with the included executable (load)   program    is received as attached file from IBM SCRT Support Team via  e-mail   for renaming duplicate  SYSIDS in SMF summary file.

After saving the attached  binary file  rensysio.bin from e-mail to PC,   it is transferred (upload)  as a binary file (with FTP or TSO IND$FILE) from PC   to z/OS  library member PATTRSNW of  library BC2A.ZOS140.OPER.LIB and  adjusted as  job PATTRSNW ready to be submitted for execution.

Job PATTRSNW /in library member BC2A.ZOS140.OPER.LIB(PATTRSNW)/ renames duplicate  SYSIDS (PARM=’/BC2A*BC3A‘) in  some records from SMFIN  file with DSN=KCI08.SMF.D051112 to SMFOUT file with  DSN=KCI08.SMFR.D051112 as follows:

//PATTRSNW JOB (9999,IPO,10,10),MSGLEVEL=1,MSGCLASS=O,NOTIFY=PATTRSN,

//           REGION=1000K                                           

//    EXEC PGM=LOADER,PARM=’/BC2A*BC3A’

//SYSLOUT DD    SYSOUT=*

//SYSUT1  DD    UNIT=VIO,SPACE=(TRK,(2,2))

//* CHANGE THE FOLLOWING TO YOUR INPUT SMF DATASET

//SMFIN   DD    DISP=SHR,DSN=KCI08.SMF.D051112

//* THIS WILL CONTAIN THE INPUT DATA SET WITH THE SYSID CHANGED

//SMFOUT  DD    DSN=KCI08.SMFR.D051112,DISP=(,CATLG,DELETE),UNIT=SYSDA,

//   BLKSIZE=8192,SPACE=(TRK,(23250,600))               

//* THIS WILL CONTAIN THE INPUT DATA SET WITH THE SYSID CHANGED

//SMFOUT  DD    DSN=KCI08.SMFR.D070513,DISP=(,CATLG,DELETE),UNIT=SYSDA,

//   BLKSIZE=8192,SPACE=(TRK,(23250,600))

//SYSLIN  DD    *                                                      

ESD            TEST           F

TXT            ??}  ? ?A?&?  &?   ??   ?   ? AD??{       K {?  K {?

TXT            ? {?   ??       ??{?        {?  ?7   ?  N   {???{?K   {?

TXT   ?          A   ?   $ A{   ]      ?7   ??0{?  ? {?   ??     ??  q?

………………………………………………………………

TXT   ;                    “8

TXT   {

RLD                           r   ?   R

END                            1566896201 020106090

After renaming SMF files of LPAR BC3A with   SYSID BC2A as  SYSID  BC3A  and concatenating  the renamed SMF data of LPAR BC3A with the SMF data  of LPAR BC2A and LPAR BC1B, the resulted summary  SMF extract data file is  passed to SCRT program to be  processed  successfully for the  3 LPARs: BC2A, BC3A and BC1B.

The same technology may be used for any ZOS executable (load) program module that  is prepared on one local Mainframe, transferred via e-mail  and  executed on another remote Mainframe.

                    1.2. Receive   new   Version of SCRT executable module from IBM LMS WEB site

Using    link http://ibm.com/systems/z/swprice/subcap/scrt/download.html      to IBM  LMS Web site for receiving the new version of SCRT tool,   choose “download”  then “Download SCRT for z/OS” . Then    enter  your  IBM  ID (usual this is your  e-mail),   enter  your PW (silva123)   and  press   “Sign in”.   You must   check  the box  “I agree”   and confirm “ I confirm  before  passing over  the  texts  “Download  now”  to  reach  the moment of  “save”. You should  browse  and  find  the directory on your PC  (d:\admin\sysprog\ibm_tool\stef_download\scrt_21.2.1 )  where to  “ save”  the new SCRT module SCRTTOOL21.2.1   as  scrttool.exe. After  2 times  click on scrttool.exe, a new   binary file  scrttool.bin is created.

After downloading  scrttool.exe from  IBM  LMS Web site to PC,  the created binary file  scrttool.bin    is transferred (upload) as a binary file (with FTP or TSO IND$FILE)  from PC  to z/OS  library member SCRT2121 of  library BC2A.ZOS140.OPER.LIB and  adjusted as  job SCRT2121 ready to be submitted for execution as follows:

– On TSO “b” session –  Enter –    p.6  (ISPF Command Shell)

– In DOSprompt of   PC/Windows enter:

D: cd admin\sysprog\ibm_tool\stef_download\scrt_21.2.1 /copy this line from here and paste to DOS prompt/ – Enter.

Send  scrttool.bin  b: BC2A.ZOS140.OPER.LIB(SCR21V21) /copy from here and paste to DOS prompt/ – Enter.

The member SCR21V21 is adjusted in member SCRT2121 to be ready for execution as job SCRT2121  according  the user environment during the next monthly SCRT report  as follows:

//SCRT2121 JOB (9999),MSGCLASS=O,NOTIFY=HLQ,REGION=0M,TIME=(5,0)

//*       

//DELETE   EXEC  PGM=IEFBR14                            

//DD1      DD    DSN=HLQ.SCRTTOOL.CSV,DISP=(MOD,DELETE),

//                   SPACE=(TRK,(1)),UNIT=(3390,1),VOL=SER=SP1789      

//SCRT     EXEC  PGM=LOADER                                   

//SYSPRINT DD    SYSOUT=*                                    

//SYSLOUT  DD    SYSOUT=*                                    

//* FOR SEQUENTIAL OUTPUT (ALL CPCS IN ONE DS)               

//* CHANGE SPACE PARAMETER TO SPACE=(TRK,(15,15))            

//OUTPUT   DD    DISP=(,CATLG),DSN=HLQ.SCRTTOOL.CSV,         

//             SPACE=(TRK,(15,15,15)),UNIT=(3390,1),VOL=SER=SP1789

//SMF      DD    DISP=SHR,DSN= HLQ.SMFEXTR.FEBXX,

//        UNIT=(3390,1),VOL=SER=SP1789

//* THE FOLLOWING DD IS FOR OPTIONAL USE BY Z/TPF CUSTOMERS  

//* //SMFUSSFS DD  PATH=’path to your data here’             

//PARMS    DD    *                                           

*                                                            

* THERE ARE 5 REQUIRED PARM KEYWORDS:                        

*     THEY MUST BE FILLED IN OR THE PROGRAM WILL NOT PROCEED.

Customer_Name=

Customer_Number=        

Contact_Name=

Contact_Email=

Contact_Phone=                                                            

………………………………………………………………………………………………………..

*   DELETE THE FOLLOWING STMTS IF Z/OS IS *NOT* RUNNING ON THE CPC

* NETVIEW PERF MONITOR V2

5655-043=*NONE or *ALL

……………………………………………………………………………………………………….

//SYSLIN   DD    *                                                

.ESD      ..  ..SCRTTOOL……..SCRTDATA….    SCRTVSE ….

.TXT …  ..  ..??}. .1??01?SCRTTOOL21.2.1

.TXT …  ..  ..Licensed Materials – Property of IBM

.TXT ..?  ..  ..SubCapacity Reporting Tool V21 (SCRT)

.TXT ..?  ..  ..Copyright IBM Corp. 2001, 2013 All Rights Reserved.

……………………………………………………………………………………………………………….

.TXT …  ..  ..q?}..».??2..&?..??..??..q.}..»

.TXT …  ..  ……

.RLD      ..    ………..?…<…&……………….?…&…*…?…?

.RLD      ..    ……..

.END                            1569623400 010613112

                     1.3. Receive  source  program VBSFIX to remove bad SMF records via IBM support  e-mail

 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 on the monthly SCRT report processing  as ABEND002 with rc=0004.

The solution of this problem  is to use the program  VBSFIX     received from IBM  SMF Level 2 Support  as   attached file vbsfix_Source.txt.

The attached character  file  is   saved on PC as file vbsfix_Source.txt. This is an Assembler source program that is transferred from PC  to local Mainframe in character format  using FTP or  with TSO/IND$FILE via ‘send vbsfix_Source.txt   a: BC2A.ZOS140.OPER.LIB(VBSFIXA) ascii crlf’  into   library BC2A.ZOS140.OPER.LIB as member VBSFIXA. The following  JCL in the member ASSBATCH of library BC2A.ZOS140.OPER.LIB is used  to assemble, Link Edit the source program in member VBSFIXA and catalog   it  as a load program  VBSFIXA  into  library  BCI05.LIB.BASE.LOAD:

//ASSBATCH JOB TIME=1440,

//         NOTIFY=&SYSUID,

//         REGION=6500K,

//         CLASS=B,

//         MSGCLASS=X,

//         MSGLEVEL=(1,1)

//*——————————————————————-

//*  ASSEMBLER JCL – 07/2003                                         –

//*                                                                  –

//*  CHANGE PARMS BELOW:                                             –

//*  BCCSLIB  = SOURCE LIBRARY                                       –

//*  BCCTLOAD = LOAD LIBRARY                                         –

//*  BCCMEMBR = SOURCE AND OUTPUT MEMBER NAME                        –

//*——————————————————————-

//       SET  BCCSLIB=‘BC2A.ZOS140.OPER.LIB’      ** SOURCE LIBRARY

//       SET  BCCTLOAD=‘BCI05.LIB.BASE.LOAD’       ** LOAD LIBRARY

//*      SET  BCCTLOAD=’BCI05.LIB.BASE.OBJECT’     ** OBJ  LIBRARY

//       SET  BCCMEMBR=VBSFIXA                     ** MEMBER

//*——————————————————————-

//*- JCL BELOW                                                       –

//*——————————————————————-

//ASM      EXEC PGM=ASMA90,

//             PARM=’OBJECT,XREF(SHORT),NODECK,NORENT’

//SYSLIB   DD   DSN=SYS1.MACLIB,DISP=SHR

//SYSUT1   DD   DSN=&&SYSUT1,UNIT=3390,SPACE=(1700,(900,900)),

//             SEP=(SYSLIB)

//SYSUT2   DD   DSN=&&SYSUT2,UNIT=3390,SPACE=(1700,(900,900)),

//             SEP=(SYSLIB,SYSUT1)

//SYSUT3   DD   DSN=&&SYSUT3,UNIT=3390,SPACE=(1700,(900,900))

//SYSPRINT DD   SYSOUT=*,DCB=BLKSIZE=1089

//SYSLIN   DD   DSN=&&OBJSET1,UNIT=3390,SPACE=(80,(200,50)),

//             DISP=(,PASS),DCB=BLKSIZE=3120

//SYSIN    DD   DSN=&BCCSLIB(&BCCMEMBR),DISP=SHR,

//             FREE=CLOSE

//LKED     EXEC PGM=IEWL,COND=(4,LT,ASM),

//         PARM=’RENT,MAP,LET,LIST,NCAL’

//SYSLIN   DD   DSN=&&OBJSET1,DISP=(OLD,DELETE)

//SYSUT1   DD   DSN=&&SYSUT1,UNIT=(3390,SEP=(SYSLIN,SYSLMOD)),

//             SPACE=(1024,(50,20))

//SYSPRINT DD   SYSOUT=*

//SYSLMOD  DD   DSN=&BCCTLOAD(&BCCMEMBR),DISP=SHR

//STGO     EXEC PGM=&BCCMEMBR

//STEPLIB  DD   DSN=BCI05.LIB.BASE.LOAD,DISP=SHR

//         DD   DSN=KCI55.LIB.PROD.LOAD,DISP=SHR

//*SNDUMP   DD   SYSOUT=*

//

The execution of the load  program VBSFIXA is performed by JCL  job VBSFIXE (EXEC PGM=VBSFIXA) using as input the bad file KCI08.SMFR.D051112 and the valid records are copied to output good  file KCI08.SMFRF.D051112. Invalid segments are converted to VB output badrecs file KCI08.SMFRFB.D051112.

//VBSFIXE  JOB (9999,IPO,10,10),MSGCLASS=O,NOTIFY=HLQ,REGION=5M

//STEPNAME EXEC PGM=VBSFIXA 

//SYSPRINT DD  SYSOUT=A

//SYSIN    DD  *                                               S

//STEPLIB  DD  DSN=BCI05.LIB.BASE.LOAD,DISP=SHR

//INPUT    DD  DSN=KCI08.SMFR.D051112,DISP=SHR

//OUTPUT   DD  DSN=KCI08.SMFRF.D051112,

//             DCB=(RECFM=VBS,

//             LRECL=32760,

//             BLKSIZE=32760),

//             UNIT=(3390,1),

//             SPACE=(TRK,(700,600)),

//             DISP=(NEW,CATLG,DELETE)

//BADRECS  DD  DSN=KCI08.SMFRFB.D051112,

//             DCB=(RECFM=VB,LRECL=32756,BLKSIZE=32760),

//             UNIT=(3390,1),

//             SPACE=(TRK,(700,600)),

//             DISP=(NEW,CATLG,DELETE)

 

The repared file  KCI08. SMFRFB.D051112    with  only  valid SMF records (bad SMF records are removed) is  used  during the SCRT processing  that  finished  OK

 with cc=0000.

 

                    1.4. Receive TRSMAIN utility program to compress data exchanged using   IBM support WEB site

TRSMAIN is a utility program to compress (terse) and decompress data exchanged using the IBM support WEB site. There are two steps required to use the TRSMAIN utility:

– Download the binary source file to the z/OS system.

– Install the utility using the TSO RECEIVE command.

Prior to downloading you must review and accept the License agreement. Click here to review the license agreement.

To download TRSMAIN directly to your workstation, click on the link below and use the browser’s “file” “save as” to save the binary file on your workstation:

TRSMAIN for z/OS or OS/390 (trsmain.bin)

Once the file is on the workstation (as file  trsmain.bin on PC), it must be uploaded to the Host system (MF). The trsmain.bin file is in binary format on your workstation and  you need to upload it to your z/OS Host. You MUST upload this file into a RECFM=FB LRECL=80 BLOCKSIZE=3120 dataset in order to extract it correctly as follows:

– From the DOS command prompt enter: D: ftp 10.212.4.90 (IP for LPAR BC2A/90)

– At the USER prompt, enter: BCA1MGP

– At the password prompt, enter: yana1

– At the Command: prompt, enter: bin

– At the Command: prompt, enter:

   quote site recfm=fb lrecl=80 blksize=3120 tracks pri=3 sec=3

– At the Command: prompt, enter: put trsmain.bin 'SOURCE.LIB'

– At the Command: prompt, enter: quit

* The host dataset name ('SOURCE.LIB') must be in quotes and capitals  in compliance with host dataset name conventions.

Once the file has been uploaded to a dataset  SOURCE.LIB (containing TRSMAIN) on the host  you must use the TSO RECEIVE command from your TSO session to convert the TRSMAIN program back into its load module format as follows:

–       From the TSO command line, issue:  RECEIVE INDSN(‘SOURCE.LIB’) command that  will generate these messages:

INMR901I Dataset PTFLCG.TERSE409.LOADLIB from NHAN on PLPSC

INMR902I Members: TRS414 TRSMAIN

INMR906A Enter restore parameters or ‘DELETE’ or ‘END’

Enter ‘END’ and press Enter. The following messages appear:

 IEB1135I IEBCOPY  FMID HDZ11G0  SERVICE LEVEL UA07761  DATED 20031212 DFSMS 01.

3.00 z/OS    01.04.00 HBB7707  CPU 2066

IEB1035I BCA1MGP  $SYSADM  $SYSADM  13:55:47 WED 14 NOV 2012 PARM=”

COPY INDD=((SYS00157,R)),OUTDD=SYS00156

IEB1013I COPYING FROM PDSU  INDD=SYS00157 VOL=WRKC01 DSN=SYS12319.T135546.RA000

BCA1MGP.R0107287

IEB1014I           TO PDS  OUTDD=SYS00156 VOL=BC2MCC DSN=PTFLCG.TERSE409.LOADLI

IEB167I FOLLOWING MEMBER(S) LOADED FROM INPUT DATA SET REFERENCED BY SYS00157

IEB154I TRSMAIN  HAS BEEN SUCCESSFULLY LOADED

IEB154I TRS414   HAS BEEN SUCCESSFULLY LOADED

IEB1098I 2 OF 2 MEMBERS LOADED FROM INPUT DATA SET REFERENCED BY SYS00157

IEB144I THERE ARE 11 UNUSED TRACKS IN OUTPUT DATA SET REFERENCED BY SYS00156

IEB149I THERE ARE 5 UNUSED DIRECTORY BLOCKS IN OUTPUT DIRECTORY

IEB147I END OF JOB – 0 WAS HIGHEST SEVERITY CODE

INMR001I Restore successful to dataset ‘PTFLCG.TERSE409.LOADLIB’

Members TRSMAIN and     TRS414 are restored in library PTFLCG.TERSE409.LOADLIB with the following parametrs:

Data Set Name  . . . : PTFLCG.TERSE409.LOADLIB

General Data                                           Current Allocation

Volume serial . . . :                BC2MCC                   Allocated blocks  . : 12

Device type . . . . :                 3390                          Allocated extents . : 1

Organization  . . . :                PO

Record format . . . :               U

Record length . . . :               0

Block size  . . . . :   13030                       Current Utilization

1st extent blocks . :               12              Used blocks . . . . : 10

Secondary blocks  . :           14              Used extents  . . . : 1

Creation date . . . :                 2012/11/14

Referenced date . . :             2012/11/14

Expiration date . . : ***None***                                                 

The executable load module TRSMAINJ is used in the following job TRSMAINJ  (with EXEC PGM=TRSMAIN)  to  condense the input  file RMF.BC2A.MONIII.DS03.UNLOAD  as output condensed  file PRINT01.MONIII.DS03.CONDNS as follows:

//TRSMAINJ    JOB MSGLEVEL=(1,1),MSGCLASS=X,TIME=1440

//***

//*  PTFLCG.TERSE409.LOADLIB

//STEPNAME  EXEC PGM=TRSMAIN,PARM=’SPACK’

//STEPLIB   DD DISP=SHR,DSN=PTFLCG.TERSE409.LOADLIB

//SYSPRINT  DD SYSOUT=*,DCB=(LRECL=133,BLKSIZE=12901,RECFM=FBA)

//INFILE    DD DISP=OLD,DSN=RMF.BC2A.MONIII.DS03.UNLOAD

//OUTFILE   DD DCB=(RMF.BC2A.MONIII.DS01.UNLOAD,RECFM=FB,LRECL=1024),

//          DSN=PRINT01.MONIII.DS03.CONDNS,

//             SPACE=(TRK,(100,30)),DISP

=(NEW,CATLG,DELETE)

/*

          2. Send Logon TSO time delay  exchange data

During TSO logon of any TSO user  after entering TSO UID, PW  and the appearance of  the  initial system messages,  more  than 30 seconds  time delay was passing   before the message ‘***’ to appear. Pressing Enter   after the message ‘***’ –   more  than 30 seconds were  passing  before the first ISPF logon menu panel  to appear. This TSO  time delay arised  unexpectedly  when Cobol program was  processing enormous data and it was necessary  to  discover  what kind of actions  provoked  this  to  happen.

The customer was advised  to send the following documentation: 
- Job list of the Cobol job from today. 
- SVC dump of the current situation when Cobol job is finished, but problem with slow responses remain. 
- RMF III VSAM data sets since the time of IPL   until present   time.

 

                    2.1. Send job list of Cobol job execution

The  JES2 processing output of job JGL11N  (that caused TSO logon delay and delayed itself with TOTAL ELAPSED TIME= 274.9) can be transferred from JES queue as  file JGL11N.txt to  PC using the following  PC files – ftp_90.bat and ftp_90.txt:

JGL11N   JOB08928 BCA1MGP     1 PRINT      A  2325:

– Prepare file ftp_90.bat

In  directory D:\admin\sysprog\ibm_tool\smf_process\smf_bc2a_jobs the file ftp_90.bat has  the following contents:” ftp – s:D:\admin\sysprog\ibm_tool\smf_process\smf_bc2a_jobs\ftp_90.txt> D:\admin\sysprog\ibm_tool\smf_process\smf_bc2a_jobs\ftpmch.err”

–  Prepare file ftp_90.txt

In  directory D:\admin\sysprog\ibm_tool\smf_process\smf_bc2a_jobs file ftp_90.txt has  the following contents:

open 10.212.4.90

BCA1MGP (TSO user ID)

yana1  (TSO user PW)

literal site sbd=BCA1VTF.FTP.TCPXLBIN

literal site file=jes jesjobn=JGL11* jeso=BCA1MGP

get JOB08928 JGL11N.txt

disconnect

quit

JGL11* – job name prefix in MF

            BCA1MGP – TSO user ID in MF

JOB08928  – job number in MF

JGL11N.txt  – file name on PC

 

–  Start File ftp_90.bat from directory D:\admin\sysprog\ibm_tool\smf_process\smf_bc2a_jobs

The results of operations are registrated in file ftpmch.err of directory D:\admin\sysprog\ibm_tool\smf_process\smf_bc2a_jobs as follows:

ftp> Connected to 10.212.4.90.

open 10.212.4.90

220-FTPD1 IBM FTP CS V1R4 at BC2AJES, 13:21:08 on 2013-04-02.

220 Connection will close if idle for more than 5 minutes.

User (10.212.4.90:(none)):

331 Send password please.

 

230 BCA1MGP is logged on.  Working directory is “BCA1MGP.”.

ftp> literal site sbd=BCA1VTF.FTP.TCPXLBIN

200 SITE command was accepted

ftp> literal site file=jes jesjobn=JGL11* jeso=BCA1MGP

200 SITE command was accepted

ftp> get JOB08928 JGL11N.txt

200 Port request OK.

125 Sending all spool files for requested Jobid

250 Transfer completed successfully.

ftp: 7385 bytes received in Seconds Kbytes/sec.

ftp> 6.041.22disconnect

221 Quit command received. Goodbye.

ftp> quit

 

– File JGL11N.txt is received on PC in directory “D:\admin\sysprog\ibm_tool\smf_process\smf_bc2a_jobs” comprising all JES2 outputs of job JGL11N   JOB08928 BCA1MGP as follows:

JESMSGLG JES2                 2 BCA1MGP  X LOCAL  22

JESJCL   JES2                     3 BCA1MGP  X LOCAL       21

JESYSMSG JES2                 4 BCA1MGP  X LOCAL  50

SYSOUT   STEP4              101 BCA1MGP  X LOCAL   1 (write records=007535031)

– The file JGL11N.txt is attached and sent via e-mail.

                     2.2. Send SVC dump  condense data

When SVC dump is needed for analysis of the current situation when Cobol job is finished, but problem with slow responses remain do the following steps.

– Produce SVC dump SYS1.BC2A.DMP00004

SVC dump SYS1.BC2A.DMP00004 (Long TSO response – 02.04.2013) is captured  on  Tuesday, 02.04.2013  and   sent as condense file ‘PRINT01.SYS1.BC2A.DMP00004.CONDNS’ on Monday, 03.04.2013 to the ECuRep.

The dump parameters from master console of LPAR BC2A /IT 7 km/ were as follows:

DUMP COMM=(Long TSO response – 02.04.2013)

R 9, JOBNAME=(TSO,JTRTDIBA,JTRLOAN,JTRCKIBA,RESDBCK0,RESDBCK1), SDATA= (ALLNUC,PSA,RGN,SQA,TRT,CSA,SUM),END

The following messages appeared:

IEE600I REPLY TO 0009 IS;JOBNAME=(TSO,JTRTDIBA,JTRLOAN,JTRCKIBA,RESD

IEA794I SVC DUMP HAS CAPTURED: 940

DUMPID=001 REQUESTED BY JOB (*MASTER*)

DUMP TITLE=LONG TSO RESPONSE -02.04.2013

IEF196I IGD101I SMS ALLOCATED TO DDNAME (SYS00005)

IEF196I         DSN (SYS1.BC2A.DMP00004                          )

IEF196I         STORCLAS (SCFAST) MGMTCLAS (MCMIG) DATACLAS (        )

IEF196I         VOL SER NOS= DMPC01

IEF196I IGD104I SYS1.BC2A.DMP00004                           RETAINED,

IEF196I DDNAME=SYS00005

IEA611I COMPLETE DUMP ON SYS1.BC2A.DMP00004 947

SYS1.BC2A.DMP00004                             2974  100   1  3390

Condense file SYS1.BC2A.DMP00004

Job TRSMAINJ  is used   to  condense the input  file SYS1.BC2A.DMP00004  as output condensed  file ‘PRINT01.SYS1.BC2A.DMP00004.CONDNS(condensed  from 2974 trk to 547.5 = 750/73% trk changing recfm from  VB to FB and lrecl from 32756 to 1024).

– Download condense file ‘PRINT01.SYS1.BC2A.DMP00004.CONDNS’ from MF to PC

After data set is tersed (condensed) this  file is downloaded from MF to PC file as follows:

From TSO/ISPF – p.6 – ActionsReceive File From Host

Host file: PRINT01.SYS1.BC2A.DMP00004.CONDNS

PC File:  d:\PRINT01.SYS1.BC2A.DMP00004.CONDNS

            Transfer Type: binary

Options: MVS/TSO – Transfer Type: binary – Record Format: Fixed – Logical Record Length: 1024

             Binary condensed file PRINT01.SYS1.BC2A.DMP00004.CONDNS is received from MF on PC as d:\ PRINT01.SYS1.BC2A.DMP00004.CONDNS (30049 KB).

Send file d:\ PRINT01.SYS1.BC2A.DMP00004.CONDNS to ECuRep

The received  file d:\ PRINT01.SYS1.BC2A.DMP00004.CONDNS was sent to ECuRep using link

 http://www.ecurep.ibm.com/app/upload

with the following parameters:

PMR number:*   13139,644,644 (13139 – PMR  /Problem TSO long response – given by IBM/,  644 Branch office number, 644IBM/BG  country code)Upload is for:*  MVS

Email address: xxxxxxxxxx

Continue  – press it   – Browse to find  d:\ PRINT01.SYS1.BC2A.DMP00004.CONDNS  – Submit

 – Confirmation message from ECuRep

The confirmation  for  the  successful upload from   ECuRep   team was as follows:

Dear Customer,

your upload was successful. We received 1 file(s):

File: 13097.644.644.PRINT01.SYS1.BC2A.DMP00004.CONDNS     30770176 bytes

 

                     2.3. Send monitoring condense data

      - Start/stop RMFGAT 
         RMFGAT is started to  gather TSO delay information  (with /F  RMF,START III)  since the time of IPL  until stop  time with the following  last 3 files active:
         
         ACTIVE -  'RMF.BC2A.MONIII.DS03’ (from 06:03:20.32 h/date 13.05.2013)
         ACTIVE -  'RMF.BC2A.MONIII.DS02’ (from 00:28:20.48 h/date 14.05.2013)
            ACTIVE -  'RMF.BC2A.MONIII.DS01’ (from 18:43:23.20 h/date 14.05.2013) – last, current
                         
         Stopped (Wednesday, at 11:49:11.98 on 15.05.2013) RMFGAT to gather TSO delay information     (with /F  RMF,STOP  III).
 
 

– Convert  the last 3 RMF III VSAM data sets to sequential files

 

TSO/ISPF – p.6 – enter:

ERBV2S  ‘RMF.BC2A.MONIII.DS01’ ‘ RMF.BC2A.MONIII.DS01.UNLOAD’ –

(from 18:43:23.20 h/date 14.05.2013) – last, current before stop RMFGAT

ERBV2S  ‘RMF.BC2A.MONIII.DS02’ ‘ RMF.BC2A.MONIII.DS02.UNLOAD’-

(from 00:28:20.48 h/date 14.05.2013) – previous

ERBV2S  ‘RMF.BC2A.MONIII.DS03’ ‘ RMF.BC2A.MONIII.DS03.UNLOAD’ –

(from 06:03:20.32 h/date 13.05.2013) – before previous

 

Condense sequential files

The sequential data sets  are tersed/condensed using job TRSMAINJ as following files:

print01.moniii.ds01.condns – (from 18:43:23.20 h/date 14.05.2013) – last

print01.moniii.ds02.condns(from 00:28:20.48 h/date 14.05.2013) – previous

print01.moniii.ds03.condns(from 06:03:20.32 h/date 13.05.2013) – before previous

 

Download condensed sequential files from MF to PC

 

After data sets are  tersed the   files above  are  downloaded from MF to PC as binary condensed files:

 

d:\ print01. moniii.ds01.condns  /19.377 MB/ – from 18:43:23.20 h/date 14.05.2013 – last

d:\ print01. moniii.ds02.condns /20.551 MB/ – from 00:28:20.48 h/date 14.05.2013 – previous

d:\ print01. moniii.ds03.condns /20.046 MB/ – from 06:03:20.32 h/date 13.05.2013 – bef.prev.

 using TSO/ISPF – p.6 – ActionsReceive File From Host …  with the  following parameters:

Host file: print01. moniii.ds01.condns

PC File:  d:\ print01. moniii.ds01.condns

            Transfer Type: binary

Options: MVS/TSO – Transfer Type: binary – Record Format: Fixed – Logical Record Length: 1024

Send 3 condense files to ECuRep

The condense files  are  sent to ECuRep using link:

 http://www.ecurep.ibm.com/app/upload

with parameters as follows:

PMR number:*   13139,644,644 (13139 – PMR  /Problem TSO long response – given by IBM/,  644 Branch office number, 644IBM/BG  country code)

Upload is for:*  MVS

Email address: xxxxxxxxxx

Continue  – press it   – Browse to find:

 d:\ print01. moniii.ds01.condns

d:\ print01. moniii.ds02.condns

d:\ print01. moniii.ds03.condns

Press – Submit

Confirmation message from ECuRep

Dear Customer,

your upload was successful. We received 3 file(s):

File: 13139.644.644.PRINT01.MONIII.DS01.CONDNS            19842048 bytes

File: 13139.644.644.PRINT01.MONIII.DS02.CONDNS            21044224 bytes

File: 13139.644.644.PRINT01.MONIII.DS03.CONDNS            20527104 bytes

           3. Send Logrec data

If  the error recording data set (ERDS also known  as LOGREC – logrec data set)  is full, then error recording stops  and z/OS continues with no error log recording. To prevent this, a daily or monthly  procedure is used to copy logrec data set (SYSPLEX.LOGREC.ALLRECS or  BC2A.LOGREC) into a daily  OUTPUT  ACCUMULATION DATA SET (IPOSAV.LOGREC) and to clear  logrec data set (SYSPLEX.LOGREC.ALLRECS or  BC2A.LOGREC)  to be ready for  new error recording followed by  printing a ‘SYSTEM SUMMARY’ REPORT for  analyzes. The OUTPUT  ACCUMULATION DATA SET (IPOSAV.LOGREC) is copied into a weekly ACCUMULATION DATA SET (IPOSAV.LOGRECW) that may be saved on tape back-ups at regular intervals. To prevent the stop of   error recording,   go to the article ZOS Logrec (Error log) processing  where the regular daily/monthly procedure for Logrec processing is described.

To download IPOSAV.LOGRECW (iposav.smf summary file) to PC and send as an attached file via e-mail to IBM z/OS support, do the following:

– Download file ‘IPOSAV.LOGRECW’ from MF to PC

this  file is downloaded from MF to PC file as follows:

From TSO/ISPF – p.6 – ActionsReceive File From Host

Host file: IPOSAV.LOGRECW

PC File:  d:\ IPOSAV.LOGRECW.bin

            Transfer Type: binary

Options: MVS/TSO – Transfer Type: binary – Record Format: Fixed – Logical Record Length: 1024

             Binary   file IPOSAV.LOGRECW.bin is received from MF on PC as d:\ IPOSAV.LOGRECW.bin (1217 KB).

The file IPOSAV.LOGRECW.bin is attached and sent via e-mail.

The text file of Logrec printout file is logrec.txt.

          4. Send SYSLOG data

Sometimes you may be required to send the current SYSLOG data for analysis.

First you have to save SYSLOG to PC. To download the current SYSLOG to PC and send as an attached file via e-mail to IBM z/OS support, do the following bellow.

From TSO/ISPF – sd.st menu –  write the command ‘xdc’ on the SYSLOG line as follows:

xdc  SYSLOG   STC06608 +MASTER+   15 EXECUTION          BC2A  BC2A

Follow  the next  screen menu to create file ‘BCA1MGP.SYSLOG’  that contains all SYSLOG data   and download  file  ‘BCA1MGP.SYSLOG’ to PC with MF-PC text file transfer as d:\syslog.txt.  Go to article JES2_ job_ processing.docx   where these operations are described in detail at item ‘2.3. xdc (save to MVS file)  RESDBCK0 JOB04443 BCA1MGP’.

            If you are required to send previous SYSLOG data  saved on daily  or weekly base, go to

the article ZOS System log – SYSLOG    where a procedure is described for daily/monthly processing of the system SYSLOG, which is written on daily file iposav.lwtr and the system SYSLOG  is cleared for new use (in TSO/ISPF – sd.log  – the size of the syslog is minimized). The file  iposav.lwtr is written to accumulation weekly file iposav.syslogw and is cleared also to be ready for the next daily or monthly use. When the accumulation weekly file iposav.syslogw is full, it is backed up on GDG tape for long time saving to be analyzed when needed.

The  weekly file iposav.syslogw (or restored GDG tape) is downloaded to PC with MF-PC text file transfer as d:\syslogw.txt.  and sent as an attached file via e-mail to IBM z/OS support.

End

 

Leave A Reply

Comments

No comments yet, be the first to add one!

Places

 

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