Re: JES2 displays captured via batch
Subject: Fw: JES2 displays captured via batch
Kenneth Klein
- Forwarded by Kenneth Klein/T00/TMMNA on 03/15/2012 08:37 AM -
Kenneth Klein/T00/TMMNA
03/15/2012 08:34 AM
To
IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu
cc
Subject
Re: JES2 displays captured via batch
/Snippage
I solve this problem by getting READ access to the Console profile in RACF
Class TSOAUTH.
Then you can establish an interactive console session as seen in the Rexx
exec below, issue the command,
and write the results to a dataset. This exec creates and displays a
temporary file
with Library management calls but that's easily changed to create a
permanent file in batch JCL.
/* REXX -*/
/* trace i? */
call Initialize
call issue_console_cmd cmd1
call endit
exit(0)
/*--*/
/* This paragraph issues commands to the console and stores the */
/* response in stem variable getmsg.*/
/*--*/
issue_console_cmd:
arg command
cartoken='JIMH'
address tso 'console name('cartoken')',
' syscmd('command') cart('cartoken')'
if RC = 56 then do
address console 'deactivate' cartoken
Say 'Console Interface Error = 'RC
say 'Terminating.'
exit(8)
return
end
DO while fc ^= 0
fc = GETMSG('getmsg.','SOL',carToken,,20)
call Process_What_Returned
END
address console 'deactivate' cartoken
return
/*--*/
/* This paragraph issues initializes variables required by this */
/* exec.*/
/*--*/
Initialize:
call Allocate_Dsn
cmd1 = $DQ
return
Process_What_Returned:
Do i = 1 to getmsg.0
queue getmsg.i
End
Return
/*--*/
/* Allocate_Dsn: This function allocates a temp file for use by */
/* our happy little exec. */
/*--*/
Allocate_Dsn:
cmd_dd1=Drandom()
ALLOC F(cmd_dd1) REUSE UNIT(VIO) SPACE(1 1) CYLINDER,
DSORG(PS) RECFM(F B) LRECL(80)
Return
Endit:
EXECIO Queued() DISKW CMD_dd1 (fini
address ISPEXEC LMINIT DATAID(DATAID) DDNAME(cmd_dd1)
address ISPEXEC VIEW DATAID(dataid)
address ISPEXEC LMFREE DATAID(dataid)
FREE F(cmd_dd1)
return
Jim Holloway - MetLife
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: IBM-MAIN Digest - 13 Feb 2012 to 14 Feb 2012 (#2012-45)
Natasa, If as you say, you are synchronously mirroring your DASD, I would make the following suggestion. Add the new CF to your current CFRM policy at your old site and acticvate. You'll have no connectivity to it so you can't allocate it locally. Your CFRM CDS gets mirrored with the updated policy and when you're ready to IPL at the new location, your system should come up, attach to the new location's CF, and use all structures currently defined. Once up for good you can clean up the old location data from your CFRM policy. For fall back purposes, shut down new, IPL old as all CF data and structures are already in place. Jim Holloway - MetLife Natasa Savinc natasa.sav...@unicreditgroup.zaba.hr; wrote on 02/15/2012 12:00:01 AM: Date:Tue, 14 Feb 2012 04:11:26 -0600 From:Natasa Savinc natasa.sav...@unicreditgroup.zaba.hr Subject: Changing sysplex hardware Hello, we are moving data center to another location. The data is already there on DASD, replicated synchronously. We plan to stop the sysplex and IPL from the replicated data , on new processor. We pretty much answered all questions so far, except for the sysplex and CF. On new location we have one new processor, that will in the end replace one of the existing processors. The configuration (LPAR names) are the same, including CF. I would like to verify following scenario: 1. For fall-back purpose: We allocate new CFRM couple data sets and prepare new set of IPL parameters. Old ones will be used if we have to IPL at old location. 2. Activate new CDS 3. Change existing policy - define different HW for the existing CF 4. Start new policy - first question is - will it report an error or will it just have pending changes for CF? 5. Shut down system (sysplex) 6. IPL on new processor Would it be better option to define different name for CF on new processor, and just add a new CF to the active policy, and in all preference lists? I hope I was clear enough, any suggestion will be appreciated. Regards, Natasa -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: zOS 32-bit ? 64-bit ?
I wrote the following rexx exec to determine what mode we were in, back
when we transitioned from 32 to 64 bit
machines.
/* REXX
*/
/* According to the manual, the FLCARCH field which is hung off the */
/* PSA at offset x'A3' or decimal 163 will be zero for an ARCHLVL of */
/* 1 (32 bit mode) and one for an ARCHLVL of 2 (64 bit mode).*/
/* This exec pulls and evaluates the value at that storage location */
/* and displays the current operating mode operating system.*/
/*--*/
/* 'WHATMODE' written on September 14, 2001 by Jim Holloway OSS */
/*--*/
/* trace i? */
cvt = Storage(11,3) /* Find out what
system we */
smca = Storage(D2x(C2d(cvt) + 197),3) /* are on and save it for */
smfid = Storage(D2x(C2d(smca) + 16),4) /* later. */
psa = 00 /* point at psa
*/
ans = c2d(storage(D2x(psa + 163),1)) /* point at FLCARCH */
test = substr(MVSVAR('sysopsys'),1,1)
select
when test = 'z' then last = Left(MVSVAR('sysopsys'),13) || '.'
when test = 'O' then last = Left(MVSVAR('sysopsys'),12) || '.'
end
select
when ans = 0 then say 'System' smfid 'is in 32 bit mode running' Last
when ans = 1 then say 'System' smfid 'is in 64 bit mode running' Last
end
exit
Jim Holloway -- MetLife
The information contained in this message may be CONFIDENTIAL and is for the
intended addressee only. Any unauthorized use, dissemination of the
information, or copying of this message is prohibited. If you are not the
intended addressee, please notify the sender immediately and delete this
message.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IBM-MAIN Digest - 6 Apr 2010 to 7 Apr 2010 (#2010-97)
Barbara Nitz wrote: Unscientific survey: How many of you use truly non-SMS-managed LOGR datasets? As in: Using the two model data sets and an IEFDB401 exit that specifies the DALLIKE text unit? Question1 : Ours are all SMS managed. Question 2: We don't share a poolfor logger datasets Jim Holloway - Met Life The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Tool for identifying mount points?
On Thu, 3 Dec 2009 17:36:36 -0600 Paul Gilmartin paulgboul...@aim.com
wrote:
Are you running it from a shell? (hint: that is a requirement)
Is that because it doesn't include RC=SYSCALLS('ON') to
define the tail variables? Why else?
Gil is correct. In order to run under, say TSO, as opposed to running
under USS,
RC=SYSCALLS('ON') is required to establish the SYSCALLS environment.
It's not required under USS as the shells establish the syscall
environment automatically.
My apologies for leaving that bit pf information out.
Jim Holloway - MetLife
The information contained in this message may be CONFIDENTIAL and is for the
intended addressee only. Any unauthorized use, dissemination of the
information, or copying of this message is prohibited. If you are not the
intended addressee, please notify the sender immediately and delete this
message.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Tool for identifying mount points?
Date:Mon, 30 Nov 2009 07:22:02 -0800
From:John Mattson john_matt...@ea.epson.com
Subject: Re: Tool for identifying mount points?
One way is to go to USS (OMVS) ISHELL from TSO and select the
File_systems option at the top and select FILE systems
But this will only show what each system has mounted. At least it gives
you a list to check.
IBM supplied a quick little rexx exec in Using Rexx and Unix Systems
Services SA22-7806-06
This exec scan the current mount table and reports back what it finds:
/* rexx */
address syscall 'getmntent m.'
numeric digits 12
do i=1 to m.0
address syscall 'statfs' m.mnte_fsname.i 's.'
j=s.stfs_avail * s.stfs_blocksize
say m.mnte_path.i''strip(m.mnte_fsname.i) '('j')'
end
Jim Holloway - MetLife
The information contained in this message may be CONFIDENTIAL and is for the
intended addressee only. Any unauthorized use, dissemination of the
information, or copying of this message is prohibited. If you are not the
intended addressee, please notify the sender immediately and delete this
message.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IBM-MAIN Digest - 23 Aug 2009 to 24 Aug 2009 (#2009-236)
On Monday, August 24, 2009 6:55 AM Barbara Nitz wrote: Let's restate the question: How many of you can use RECEIVE FROMNETWORK directly, without starting other supporting programs? We do all IBM maintenence downloads via network receive excluding our annual Serverpac install, the download for which is submitted via the Serverpac dialogs. I set up digital certificates, annually download a new key from shopz, connected all my team members to the resulting keyring. I can then submit a job requesting any of the supported download types from the batch SMPCNTL DD. I love the fact that I don't have fire up my browser and sign on to shopz in order to initiate an order. We've built this into our monthly maintenence process and use it throughout. Jim Holloway - MetLife The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re; BPXWDYN and the Internal Reader
Terry,
I believe that your problem may be in not specifying lrecl. This
Rexx
snippet shows how I code the BPXWDYN call to send an email to SMTP via the
internal reader and then off to the corporate mail servers...
Works every time.
if bpxwdyn(alloc fi(out) sysout(A) WRITER(SMTP) lrecl(80) blksize(4000)
msg(2))0 then
do
...
...
end
Jim Holloway
Sr. Software Systems Engineer
Metropolitan Life Insurance Co.
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Terry Sambrooks
Sent: Tuesday, June 30, 2009 1:19 PM
To: IBM-MAIN@bama.ua.edu
Subject: BPXWDYN and the Internal Reader (INTRDR)
Hi Folks,
I am in need of some direction from this august body.
As a bit of fun I am trying to mimic the TSO SUBMIT command available in
REXX, by using BPXWDYN in a COBOL program to dynamically allocate an
FTINCL
output file and write it to the internal reader.
Snip
The COBOL Working Storage elements are:
01 ALLOC-FT-JOB.
03 FILLER PIC X(30) VALUE
'ALLOC FI(JOBIN) SHR MSG(2) DA('.
03 FT-JOB-DSN PIC X(45) VALUE SPACES.
01 ALLOC-JES-JOB.
03 FILLER PIC X(38) VALUE
'ALLOC FI(JOBOUT) WRITER(INTRDR) MSG(2)'.
Kind regards - Terry
The information contained in this message may be CONFIDENTIAL and is for the
intended addressee only. Any unauthorized use, dissemination of the
information, or copying of this message is prohibited. If you are not the
intended addressee, please notify the sender immediately and delete this
message.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Subject: FMID descriptions
Bob, My shop does annual serverpacs and what I did was to generate the CPAC products report to a pre-allocated dataset. I then wrote an exec to parse out all the FMIDs and their plain English equivalents. We use this to provide dynamically generated web pages to publish what maintenence we've applied during a given maintenence cycle. I've also used GIMAPI and Rexx code to extract the same data from the CSI. I'd be happy to share so if you'd like so please let me know. Jim Holloway - MetLife jhollo...@metlife.com IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu wrote on 05/30/2009 12:00:03 AM: -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Richards, Robert B. Sent: Thursday, May 28, 2009 12:16 PM To: IBM-MAIN@bama.ua.edu Subject: FMID descriptions Does anyone have any REXX code to grab English description FMID table entries out of GIM.SGIMTENU's BCNFMDS member by passing it the FMID in question? I am writing some code to parse information from the ERROR SYSMODS Report and want to provide the reader with ICKDSF instead of EDU1H01, et al. I looked at the various SMP/E LIST commands, but parsing any one of those reports seems to be overkill for my purposes. Kurt Q, feel free to jump in here and tell me that it is possible run some report that just provides these two pieces of information. I looked in the archives and see that others have cut and paste some of this info from web pages or have their own lists, but am looking for something that would be automatically updated based on my product set. Other suggestions are also welcome! :-) Bob The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IBM-MAIN Digest - 7 May 2009 to 8 May 2009 (#2009-128)
Barbara, It may very well be that SYSLOG has always stopped at either $PJES2 or the Z EOD command being issued. I don't remember it that way nor does anyone else in the shop. So for us, it's something new and exciting We've updated OPERLOG to duplex so that we don't lose shutdown logs when a coupling facility may be shutdown or abnormally terminates. IBM has work to do for SMF or any CF based logstream... Logger should always harden the SMF data at shutdown to the archive datasets, currently it does not do so reliably. As for Date:Fri, 8 May 2009 00:24:50 -0500 From:Barbara Nitz nitz-...@gmx.net Subject: Re: SMF LOGGER - Not Ready for Prime Time IFA705I HALT SMF PROCESS HAS SYNCHRONIZED THE BUFFERED LOGSTREAM RECORDS. I really like the suggestion in the books for this message sarcasm off, which implies to use automation on a 'NOT synchronized' message, even after a z eod. Strangely, z eod is only issued in this installation after *all* address spaces are gone (well, those visible on a d a,l). So no automation. I realize that this message is also issued for switch smf commands. that we discovered that IBM now stops SYSLOG at two points. When either Z EOD is issued or when JES2 is stopped. The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: SMF LOGGER - Not Ready for Prime Time
Jim, I have seen the same problem, BUT, only when our coupling facilities are also shutdown as well. If the couplers remain up, you should not experience data loss and logstream corruption. What I see in the log after a Z EOD is issued is IFA705I HALT SMF PROCESS HAS SYNCHRONIZED THE BUFFERED LOGSTREAM RECORDS. This tells me that the SMF buffers are flushed to the logstream where they should live there happily across IPLs unless you shutdown the couplers. In my experience, this happens mostly when ICFs are used and the CECs the ICFs live on are POR'd frequently. We have moved away from ICFs except for our lab and GDPS environments for just this reason (and DB2 datasharing). In both those cases, our SMF output is small enough that we can easily duplex the logstreams and not lose any data. If this is an option for you, try duplexing. When it happened to us, we lost some DB/2 SMF data and OPERLOG. This was significant for us because it was during this failure that we discovered that IBM now stops SYSLOG at two points. When either Z EOD is issued or when JES2 is stopped. Thus I had no log data neither from SYSLOG nor OPERLOG. I pointed out this inconsistency to IBM and I was also directed to pursue a Marketing Request via our local IBM support. I'm told that the Marketing Request approach causes IBM to poll it's user community and see how many accounts are affected. Then they can use that data make a decision whether or not to fix the problem. Jim Holloway - MetLife -- Date:Wed, 6 May 2009 06:59:00 -0500 From:Jim Marshall jim.marsh...@opm.gov Subject: SMF LOGGER - Not Ready for Prime Time If anyone is in the throws of putting the SMF LOGGER into production, I would seriously hold up and wait a while. We have been up on it for about three months and have gone through one problem, hurdle, consequence, challenge, etc, after another. Today the issue is with when you shutdown a system or worse if you need to bring down the entire sysplex. Z EOD does not interface to the SMF LOGGER and the operators usually blow the systems away when they receive the message which says EOD is done. The significance is the logger is still doing its thing and now break it; causing all kinds of grief later. IBM has a temporary fix where you issue a set of commands per LPAR before the Halt EOD but so far they have not worked. Besides so far, the commands do not tell you when the logger is completed doing its think. Although when the set of commands do work, hopefully it will tell an operator something of its completion. Remember, the intent of this is for your operators to visit every LPAR shutting down and wait for each. This will bring new meaning tothe idea of a fast sysplex wide IPL. Everyone including IBM agrees Z EOD needs to be tap everyone on the shoulder to have its logger to do what it should do and then tell HALT, it is now done; thus giving the message which is now real. So to do this, we are submitting as Marketing Request to IBM to get all the players to talk to each other to sort through this situation (not to be confused with a problem). Things are working as intended except no one thought this all the way through and the cardinal word is intended. Will keep you posted as things unravel. jim (WashDC) The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Decreasing an HFS
Dennis, I would approach this from the other direction and allocate your down-sized HFSs at the space you desire, mount them along with your source HFSs, and copy from source to destination with PAX. Mount your Java file systems at their usual locations, create and mount your downsized file systems at another mountpoint in your filesystem (we use /service with our various target set directories underneath it.) Using my example: Mount your new OMVS.CPAC.ZOSAR1.JV390.NEW at /service/J1.4 Get into the shell and cd into /usr/lpp/java/J1.4 Issue pax command pax -p e -rwX . /service/J1.4 Upon completion, unmount both file systems, rename original to .OLD rename new to original and remount. Jim Holloway - MetLife -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Dennis McCarthy Sent: Tuesday, April 21, 2009 1:06 PM Subject: Decreasing an HFS Environment: Testing z/OS 1.9 I use FDR to copy my HFS file systems when doing maintenance. I was able to successfully copy them (JV390, JAVA64V5 and JAVA64V6) to a larger size, but now that I see I've over allocated then, I want to copy again to a smaller size. They are currently 25,000 tracks each with a max of 16% used. Pre- allocation of even 10,000 tracks results in an INSUFFICIENT SPACE error message: FDR111** VOL=HFSZ01,DSN=OMVS.CPAC.ZOSAR1.JV390 HAS INSUFFICIENT SPACE ALLOCATED - 01 TRACKS FDR111** NUMBER OF TRACKS NECESSARY=025000 FDR111** EXTENT CYL=01112 TRK=08,CYL=02199 TRK=04 FDR111** EXTENT CYL=02308 TRK=01,CYL=02887 TRK=13 FDR326** COPYENDED WITH NO DATA SETS COPIED VOL=HFSZ01 If I allow FDR to allocate, it will attempt to get the 25,000 tracks, and I don't have the space on DASD. As an absolute last resort, I can get another pack, but I'd rather not. Suggestions? The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: one IKJEFT01 job, 2 outputs in sdsf - why?
Sean,
The IKJEFT01 / OSHELL combination produces two sysouts because
ishell allocates STDOUT to a temporary file under /tmp then invokes
BPXBATCH SH to run the desired command. DD OSHOUT1 is allocated and
STDOUT copied to it. This dynamic allocation results in the
separated SYSOUT.
I've taken to using the IBM supplied module BPXWUNIX to execute
shell commands, execs and programs. I built a tiny
five line Rexx exec to setup and call BPXWUNIX and one of it's options is
to specify an output DD. I also use it in Rexx as a procedure
when it's necessary to interface with USS from the MVS side of the house
because of its small size. 5 lines of code vs 107 for OSHELL.
My Rexx looks like this
/*Rexx */
Parse Arg uss_cmd
Call Bpxwunix uss_cmd,, DD:SYSTSPRT
If result0 Then Say Rc(!!result!!)
Exit result
The JCL to invoke it looks like this:
//xxx JOB ('USSCMD'),MSGCLASS=O,NOTIFY=SYSUID,REGION=0M
//TSOBATCH EXEC PGM=IKJEFT1A
//SYSEXEC DD DSNAME=UNIX.REXX.EXEC,DISP=SHR
//SYSTSPRT DD SYSOUT=*,LRECL=256,RECFM=V
//SYSTSIN DD DATA,DLM=##
usscmd ls -E /u/jim/
##
The net result is all output from the ls command goes to the SYSTSPRT DD.
A word of caution, execution BPXWUNIX does not result in a shell being
instansiated so there is no inherited path for BPXWUNIX to search.
Therefore you must supply the path to the resource to be executed except
for internal shell commands. For example, if you wanted to
execute the chmount external command, the call might be usscmd
/usr/sbin/chmount -R -a /tmp/
with the full path to the directory where chmount lives.
Doc for BPXWUNIX can be found at
ftp://ftp.software.ibm.com/s390/zos/tools/rexx/rexxfunc.html
Jim Holloway - Metlife
Smith, Sean M sean.m.sm...@bankofamerica.com wrote on 03/09/2009
14:37:28 PM:
--
Date:Mon, 9 Mar 2009 14:37:28 -0700
From:Smith, Sean M sean.m.sm...@bankofamerica.com
Subject: Re: one IKJEFT01 job, 2 outputs in sdsf - why?
I would like to second the question...I understand that the second
execution is from the spawned task but is there a way to get the
output to come back into the originating execution?
All that being said, in your example you could use this instead:
//STEPNAME EXEC PGM=BPXBATCH,PARM='SH ls -la /etc/ | cat'
//STDOUT DD SYSOUT=*
//STDERR DD SYSOUT=*
Sean Smith
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Bonno, Tuco
Sent: Monday, March 09, 2009 12:04 PM
To: IBM-MAIN@bama.ua.edu
Subject: one IKJEFT01 job, 2 outputs in sdsf - why?
cross-posting to ibm-main, mvs-oe
running z/os 1.9
when I run this job:
//tucopgp1 jobâ?¦ msgclass=x â?¦..
//abc exec pgm=IKJEFT01
//sysexec dd disp=shr, dsn=sys1.sbpxexec
//systsprt dd sysout=*
//systsin dd *
OSHELL ls â??la /etc/ | cat
the output shows up as TWO entries in sdsf each w/ the same jobnameand
jobid:
(e.g.,)
tucopgp1job10694â?¦.. tot-rec = 85
tucopgp1job10694 â?¦..tot-rec =90
the 90-line item is the conventional jes2 stuff (log, msg-s, jcl,
systsprt) ;
the 85-line item contains the output proper of the omvs â??catâ?
command.
what should I add to my jcl to have all the ouput conflated into
just one item in sdsf ?
thank you.
The information contained in this message may be CONFIDENTIAL and is for the
intended addressee only. Any unauthorized use, dissemination of the
information, or copying of this message is prohibited. If you are not the
intended addressee, please notify the sender immediately and delete this
message.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IBM-MAIN Digest - 31 Dec 2008 to 1 Jan 2009 (#2009-1)
Lizette, It seems that the behavior I described is the expected behavior for the console service if either BPX.CONSOLE is not defined or it is defined but the caller does not have the proper permissions. At my shop, BPX.CONSOLE is not defined so I receive the BPXM023I message with the callers ID prefixed to the message. This behavior is described in UNIX System Services Programming: Assembler Callable Services under the discussion of the _console service. I added the BPX.CONSOLE profile on my sandbox system and restarted EKM and got the messages in the form you did. The solution for you would seem to be to either remove the profile or the EKM server IDs access to it. Jim Lizette Koehler stars...@mindspring.com wrote on 01/01/2009 09:36:46 Date:Thu, 1 Jan 2009 09:30:46 -0500 From:Lizette Koehler stars...@mindspring.com Subject: Re: Shell Scripts in EKM Yes we are running JZOS batch loader and EKM as an STC. However, we have no BPXM023I messages. Only the text of the messages. I have asked IBM about this and they indicated it has to do with the BPX.CONSOLE profile. How is yours set for EKM STC? Is EKM STC in the access list? Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Jim Holloway Sent: Thursday, January 01, 2009 9:23 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Shell Scripts in EKM Are you running the EKM Server under MVS with JZOS batch loader? While I agree with you both concerning the lousy messaging, running the EKM Server as a started task with the batch loader modifies the message enough for automation (we use BMC) to pickup on the fact that EKM is up and available. When we start EKM we get the following: 08363 02:52:24.47 STC09716 000A0294 BPXM023I (EKMSERV) Processing 08363 02:52:24.47 STC09716 0090 BPXM023I (EKMSERV) Server is started 08363 02:52:24.47 STC09716 000A0294 BPXM023I (EKMSERV) Server is running. TCP port: 3801, SSL port: 5443 08363 02:52:24.47 STC09716 000A0294 BPXM023I (EKMSERV) Server is running. TCP port: 3801, SSL port: 5443 We key off the BPXM023I message looking for EKMSERV Jim Holloway - MetLife Hunkeler Peter (KIUK 3) wrote on 12/31/2008 10:41:13 +0100 Date:Wed, 31 Dec 2008 10:41:13 +0100 From:Hunkeler Peter (KIUK 3) peter.hunke...@credit-suisse.com Subject: Re: Shell Scripts in EKM The reason is our EMK server on z/OS V1.9 does not have any message IDs, so all we get is the following text: Server is running. TCP port: 3801, SSL port: 1443 Seems like inacceptable behaviour for a software to be run on z/OS. I'd try to open a PMR requesting identifiable messages. -- Peter Hunkeler Credit Suisse Date:Wed, 31 Dec 2008 05:40:33 -0500 From:Lizette Koehler stars...@mindspring.com Subject: Re: Shell Scripts in EKM I have already done that. A requirements hasw been accepted. But with ported applications I am not sure how long it will take for IBM to action this. Not enough z/OS Users or tape encryption to put pressure on sooner than later. So in the meantime, I am hoping a shell script could be created that will give us the message we need for automation. Lizette The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Shell Scripts in EKM
Are you running the EKM Server under MVS with JZOS batch loader? While I agree with you both concerning the lousy messaging, running the EKM Server as a started task with the batch loader modifies the message enough for automation (we use BMC) to pickup on the fact that EKM is up and available. When we start EKM we get the following: 08363 02:52:24.47 STC09716 000A0294 BPXM023I (EKMSERV) Processing 08363 02:52:24.47 STC09716 0090 BPXM023I (EKMSERV) Server is started 08363 02:52:24.47 STC09716 000A0294 BPXM023I (EKMSERV) Server is running. TCP port: 3801, SSL port: 5443 08363 02:52:24.47 STC09716 000A0294 BPXM023I (EKMSERV) Server is running. TCP port: 3801, SSL port: 5443 We key off the BPXM023I message looking for EKMSERV Jim Holloway - MetLife Hunkeler Peter (KIUK 3) wrote on 12/31/2008 10:41:13 +0100 Date:Wed, 31 Dec 2008 10:41:13 +0100 From:Hunkeler Peter (KIUK 3) peter.hunke...@credit-suisse.com Subject: Re: Shell Scripts in EKM The reason is our EMK server on z/OS V1.9 does not have any message IDs, so all we get is the following text: Server is running. TCP port: 3801, SSL port: 1443 Seems like inacceptable behaviour for a software to be run on z/OS. I'd try to open a PMR requesting identifiable messages. -- Peter Hunkeler Credit Suisse Date:Wed, 31 Dec 2008 05:40:33 -0500 From:Lizette Koehler stars...@mindspring.com Subject: Re: Shell Scripts in EKM I have already done that. A requirements hasw been accepted. But with ported applications I am not sure how long it will take for IBM to action this. Not enough z/OS Users or tape encryption to put pressure on sooner than later. So in the meantime, I am hoping a shell script could be created that will give us the message we need for automation. Lizette The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: how to write sysrexx
Scott Ford wrote Date:Fri, 7 Nov 2008 00:54:01 -0500 Subject: Re: how to write sysrexx Tommy, Here is one I wrote and its output SNIP /* Rexx*/ /SNIP I tried this also but it only return one message line, It has to do with the way the messages are returned ...I think. Hope this helps you out .. I experienced this behavior as well and I opened an ETR with IBM. IBM says axrcmd is working as designed but I found that I had to loop through responses multiple times which is documented in the Assembler Services Reference. While there is documentation in the Assembler Services Reference, it is somewhat vague and not at all intuitive. In order to capture all command output, I setup a loop which ran until there was no more data returned from axrcmd. Note that you make the initial call without the stem variable and then subsequent calls include the stem variable but not the command. This tells axrcmd to get responses from the previously entered command. cmd1 = $DU,LNES call issue_console_cmd cmd1 . . issue_console_cmd: arg command my_rc = AXRCMD(command) DO UNTIL my_rc 0 my_rc = AXRCMD(,'getmsg.',10) call Process_What_Returned END return Process_What_Returned: Do i = 1 to getmsg.0 If getmsg.i = Then getmsg.i = counter=counter+1 My_Lines.counter=getmsg.i End Return Hope this helps Jim Holloway MetLife The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: ServerPac and zFS
From:John Mattson [EMAIL PROTECTED] Subject: Re: ServerPac and zFS SNIP EZZ4203I Z/OS UNIX - TCP/IP CONNECTION ERROR FOR TCPIP-BPX1PCT,800D,,0079,11B3005A EZZ4203I Z/OS UNIX - TCP/IP CONNECTION ERROR FOR TCPIP-BPX1PCT,C005,,0079,11B3005A EZZ9315E TCP/IP WAITING FOR RESOLVER TO INITIALIZE IBM added the RESOLVER task in as a requirement round about z/OS 1.4 if memory serves. We added the parm RESOLVER_PROC(RESOLVER) to BPXPRMxx and added the RESOLVER proc to SYS1.PROCLIB, then added resolv.conf to the /etc directory which contains various TCPIP related parms. Here's ours: TCPIPjobname TCPIP DATASETPREFIX SYSP.TCPIP MESSAGECASE MIXED HOSTNAME x DOMAIN x.COM NAMESERVER 10.9.167.76 NAMESERVER 10.10.61.91 NAMESERVER 10.5.20.166 NAMESERVER 10.1.56.63 NAMESERVER 10.10.36.66 Jim Holloway - MetLife The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
[no subject]
Lizette, You would have to create IOEPRMxx and place any configuration parameters in it, but z/FS will work fine without it. I don't have an IOEPRMxx coded either. IOEAGFMT is in your SYS1.SIOELMOD library. You also need to mount the ZFS file system in BPXPRMxx like this: FILESYSTYPE TYPE(ZFS) ENTRYPOINT(IOEFSCM) ASNAME(ZFS,'SUB=MSTR')== This parm is optional, but we needed it at my shop because otherwise z/FS and JES2 waited on each other as we converted the ServerPac file systems to z/FS. We were also given a MOD 27 to do software SMP network receives and it works quite well. We had our storage team modify the ACS routines to get us to that MOD27. I realize you may have already seen responses on this, I get the daily digest form of the list, so I'm a little late. Jim Jim Holloway Sr. Software Systems Engineer Operating Systems Automation - RISC - Troy, NY Internet: mailto:[EMAIL PROTECTED] Date:Wed, 7 May 2008 15:35:38 -0400 From:Lizette Koehler [EMAIL PROTECTED] Subject: Re: ServerPac and zFS John, Thanks. So far I am not sure our environment is even setup for zFS. I was not able to find a parmlib member IOEPRMxx. Nor can I find the program IOEAGFMT in the linklst/lpalist. I may have to setup some ACS codes as well, I am not sure. Lizette The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
[no subject]
I do something very similar in my batch trail using OPC/E. I keep 2 copies of /etc/syslog.conf, syslog.conf.a, syslog.conf.b, which contain log name versions ending in either in .a or .b: *.alert /dev/console auth.* /tmp/auth.log.a *.err /tmp/error.log.a daemon.*/tmp/server.log.a *.*;auth.none;daemon.none;local7.debug /tmp/trashcan.log.a . The first step overlays /etc/syslog.conf with the next version, then I issue the kill -HUP to force syslogd to reread /etc/syslog.conf. We use SAR here so the remainder of the job copies the various logs over to JES2 and then to SAR. On Date:Thu, 1 May 2008 07:25:55 -0500 John Mckown wrote Subject: Re: ftp - syslogd - rotate I am not sure about 1.7. On z/OS 1.8, my /etc/syslog.conf file looks like: kern.* /var/log/kern.%Y-%m-%d user.* /var/log/user.%Y-%m-%d mail.* /var/log/mail.%Y-%m-%d news.* /var/log/news.%Y-%m-%d uucp.* /var/log/uucp.%Y-%m-%d daemon.* /var/log/daemon.%Y-%m-%d auth.* /var/log/auth.%Y-%m-%d cron.* /var/log/cron.%Y-%m-%d snip So that 1 second after midnight, the kill is issued. This causes syslogd to reread the /etc/syslog.conf and as a side effect pick up the new name. %Y is replaced with the 4 digit year, %m is replaced by the 2 digit month, %d is replaced by the 2 digit day. You can then run some other process to clean up old files in /var/log Jim Holloway - MetLife The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: FTP serious error... HELP!
On Wed, 16 Apr 2008 06:54:11 -0500,Cwi Jeret [EMAIL PROTECTED] wrote: We have a similar problem using the NETSAT command , on some our LPARS while on the others it work OK . The NESTAT command with parameters like HOME, DEV or ROUTE Functions OK on all Lpars... The output we get on the failing Lpars : Command === netstat EZZ2350I MVS TCP/IP NETSTAT CS V1R7 TCPIP Name: TCPIP 11:47:58 EZZ2586I --- -- - EZZ2587I 3E85854B 11:47:58 snip Check to see if your HFSs or ZFSs mounted correctly at IPL time. I've had this happen and even though I mounted the ROOT HFS/ZFS successfully after a mount failure (this is a shared ZFS environment) at IPL time, TCPIP (which was not recycled) had the symptoms described. As TCPIP was completely functional except for the displays, we had to wait until a weekend change window to correct. The problem was a typo in BPXPRM. After the IPL, the problem cleared. The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IBM-MAIN Digest - 13 Apr 2008 to 14 Apr 2008 (#2008-105)
On Mon, 14 Apr 2008 17:01:51 -0700, Skip Robinson wrote: -- Date:Mon, 14 Apr 2008 17:01:51 -0700 From:Skip Robinson [EMAIL PROTECTED] Subject: Re: SMF in System Logger In the absence of CF Sizer assistance ;-( I looked at the samples from IBM and thought they seemed awfully big. A structures occupies dedicated real storage, after all; I tend to be stingy with it. After consulting with our SMF data caretaker who saw no obvious advantage is splitting records at the collection point, I set up only a single CF structure like this that captures all records: STRUCTURE NAME(IFASMF_DEFAULT) /* SMF structure for unspecified types */ INITSIZE(1) SIZE(5) Despite occasional IXC585E 'structure full' messages, I haven't increased it from the INITSIZE value. This structure supports only one system. Another member is 1.7 (no can do), and the third is also 1.9 but a 'bronze-plex' member that does not share DASD. Haven't quite figured out how handle that puppy yet. An interesting quirk I just noticed: most (for today, all!) IXC585E messages are being issued by the other 1.9 member, which still uses MANx recording. No messages on the 1.7 guy or on the guy actually using System Logger. We have several non-parallel-sysplex systems that are candidates for DASD-only logging but haven't ventured down that road as yet. Book says it works. We're looking at multiple structures to accommodate the heavy hitters. In our shop, DB/2, the occasional (all right, frequent) CICS looper, and the fact that Audit wants us to log all access attempts to production datasets including successful attempts has caused us in the past to lose SMF data. We may adjust up or down based on our experiences. Already I've dropped the system specific structures I mentioned in an earlier post in favor of SYSPLEX versions. I take your point though and it may be overkill but I may have to prove it to our Capacity folks. The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: SMF in System Logger
On 04/14/2008 01:20 PM, Skip Robinson wrote: I presented a user session at SHARE Orlando based on experience with our z/OS 1.9 sandbox image. In the meantime, we have migrated SMF Logger to our development system, which gets very busy and therefore creates way more SMF data than the sandbox does. Everything is working fine. I still miss the Snip Skip, Thanks for the feedback. I couldn't find a manual reference for SMF Structure names either. But I am curious as to the structure sizing you're using for your development environment(If you're using the CF). I have three structures defined, type 30s, type 80s, and everything else. The lab environment I'm on is our smallest lab sysplex used for DASD Mirroring testing. So there are no type 110s or type 101s and in reality not much happens in this plex. Our primary labs have CICS and DB/2 so the volume should go up. In production, which is fairly busy, our capacity folks have reserved 8Gig in our external CFs for SMF. The SYSPLEX is a 5 system sysplex and we're looking at having five structures/logstreams per system. Also, if you are using the CF, are you duplexing the data into staging datasets? We are considering this as a Belt and Suspenders solution to help insure against dataloss. Jim Holloway Sr. Software Systems Engineer Operating Systems Automation - RISC - Troy, NY (518)285-2646 [Voice] (518)281-9686 [Cell Phone] (419)730-0857 [FAX] MetNet Lotus Notes: mailto:jholloway Internet: mailto:[EMAIL PROTECTED] The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
SMF in System Logger
We are beginning to test SMF in logstreams and so far, so good. Like others have mentioned, I really, really want the ability to delete records from the logstream programmatically after I've extracted them, but I can wait. Based on our experiences with VSAM SMF recording over the years we've decided to use a 2 day RETPD for SMF. I do, however, have some nits to pick: 1.) Logstream Structure Names: The doc is vague on what to name the structures. Every CF structure I've worked with, at the least said Structure names must begin with blah-blah. Not so here. I knew that IBM reserved the string SYS for itself when naming structures, so I arbitrarily picked SYSSMF_System_Name_Record_Type. I would've expected at the least, Name the structure whatever you want. The SMF manual refers you to the Setting up a Sysplex manual which doesn't address the specifics required for SMF. 2.) The IBM CFSizer webpage has no tools for helping you size your SMF structures. I emailed the webmaster for that page and he tells me that while IBM recognizes the need, no time frame is available as to when an SMF CFSizer tool will be available. The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
