On Sun, 26 May 2013 18:08:22 -0700 Charles Mills charl...@mcn.org wrote:
: you need to save the key prior to the MODESET KEY=ZERO invocations
:Are you sure? MODESET KEY=NZERO,... won't remember for you?
NZERO sets you to TCB key, which may not be the key the PSW was in at the time
of the ZERO.
On 5/26/2013 9:08 PM, Charles Mills wrote:
you need to save the key prior to the MODESET KEY=ZERO invocations
Are you sure? MODESET KEY=NZERO,... won't remember for you?
No, why should it? The only persistent key the system knows for you is
the TCBKEY; the current key is in the PSW, saved
Hi Graham,
DSNUPROC is aJCL procedure for executing DB2 utilities. DSNUTILB is
the DB2 utility program.
To create DB2 objetcts using DSNUTILB, you nees to use the EXEC SQL online
utility control statement.
To create your STOGROUP using DSNUPROC , your JCL woul;d be something
like :
//STEP1
Hi,
I am looking for a way to create a list of uncataloged datasets on a specific
volume.
I tried this:
//COPY EXEC PGM=ADRDSSU,REGION=3000K,PARM='TYPRUN=NORUN'
//SYSPRINT DD SYSOUT=*
//INPUTDD UNIT=3390,VOL=SER=T13R01,DISP=SHR
//SYSINDD *
COPY DATASET(INCLUDE( -
The CATLG filter is valid only when using an input volume list.
Ant.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of ??? ?? ???
Sent: Monday, 27 May 2013 5:27 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: List of uncataloged datasets
Hi,
Thanks
That solved the problem
Gadi
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Anthony Thompson
Sent: Monday, May 27, 2013 11:03 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: List of uncataloged datasets
The CATLG filter is
Hi Scott,
Pardon my Monday morning eyes that have not been stimulated with enough
caffeine, but...
After the trace record for the STORAGE OBTAIN for the Storage
address=2BDC1000, Length=204800, you mentioned that there is a STORAGE
RELEASE for 2BDC1000 in the trace but I don't see it! In
In 086801ce5a76$af711e70$0e535b50$@mcn.org, on 05/26/2013
at 06:08 PM, Charles Mills charl...@mcn.org said:
you need to save the key prior to the MODESET KEY=ZERO invocations
Are you sure?
Yes.
MODESET KEY=NZERO,... won't remember for you?
The crystal ball on channel 3 is broken. From
In 005001ce5aab$5c511c10$14f35430$@com, on 05/27/2013
at 02:25 PM, Robin Atwood abend...@gmail.com said:
Thanks for the info. The BEA can be easily retrieved from RTWA+6D0. I
also found a presentation that claimed the BEA was saved in low
memory at 110. but a few dumps I looked at did not bear
In 51a2b33f.3060...@cdpwise.net, on 05/26/2013
at 09:13 PM, Graham Hobbs gho...@cdpwise.net said:
Does that imply IKJEFT01 can't do it,
No, it implies that a hyphen is not a valid TSO command. The + or -
for continuation goes at the end of the line, not at the beginning.
--
Shmuel
Thanks, still didn't work:-( but Ron's post explained why.
On 27/05/2013 10:26 AM, Shmuel Metz (Seymour J.) wrote:
In 51a2b33f.3060...@cdpwise.net, on 05/26/2013
at 09:13 PM, Graham Hobbs gho...@cdpwise.net said:
Does that imply IKJEFT01 can't do it,
No, it implies that a hyphen is not a
#1 - IIRC, the volume in the ICH408I message for a _VSAM_ data set is
the volume name that the _catalog_ is on in which the VSAM data set is
catalogued. Not the volume name of the volume upon which the VSAM data
set exists.
#2 - I don't know. Double check that that both OMVS and BPXOINIT are
Yeah, I have too look at what has happened their trace was unreadable so I
will try the same code on our test system with a gfs trace ..I just want to
solve the mystery and make sure we don't have an issue
Scott ford
www.identityforge.com
from my IPAD
'Infinite wisdom through infinite
Hi Ron,
I used your 'something like JCL', diddled around muchly, finished up with ..
//PROCLIB JCLLIB ORDER=(DSNA10.PROCLIB)
//STEP1EXEC DSNUPROC,SYSTEM=DBAG,UID='',UTPROC=''
//DSNUPROC.SYSPRINT DD SYSOUT=(*)
//DSNUPROC.UTPRINT DD SYSOUT=(*)
//DSNUPROC.SYSINDD *
EXEC SQL
CREATE
Hello Lizette,
Got all your pointers about:
- EXEC PROC, looking into SDSNLOAD, manual refs, installation step 10, etc
- doing stuff manually on TSO screens is a non-starter; my software
kicks off by running a single JCL stream, generating and 'sub'bing new
jobs along its way (including this
On Mon, 27 May 2013 15:28:37 +0200, nitz-ibm wrote:
2 things spring to mind immediately:
1. Why is the mount via ishell looking for this ZFS on the wrong volume?
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/ichza6c1/1.4.1
The meaning of the volume serial number shown in the VOL
Does anyone know how to create a new list here at UA.EDU's listserver?
I'm searching a place to host an AFP (Advanced Function Presentation) related
list.
There was one on Topia but it seems to be dead.
--
Peter Hunkeler
--
As you do not change all the other original LPAR attributes and
connections, those will remain intact after first becoming '*'.
2013/5/19 Skip Robinson jo.skip.robin...@sce.com
As I mentioned a follow-on post, I eventually PORed to get the new IODF
active with no change other than LPAR name.
IBM Fault Analyzer support on z/OS.
Would anyone out there have obtained the ZAPs for the IEAVTABD version of the
module that came with the PTFs for OA38518?
I have searched under z/OS and under IBM Fault Analyzer and not found what is
needed.
Yes, I know I may have to open a PMR but if
Just curious. Is the zap not part of the PTF? If so, could you not go to
IBM.COM and download the PTF appropriate to your level of software? Or does
the PTF just ship the changed module?
Lizette
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
There is usually a APAR/PTF issued by IBM Fault Analyzer support that
contains the updated ZAP as a sample.
The issue is nothing to do with z/OS itself so they do not care when other
products (or vendors) come along and ZAP the z/OS modules.
regards,
Anthony Fletcher - NZ MIITP
Team Lead NZ
Guys:
I need some help I want to do a GFS trace on our 1.13 system and have done the
following:
1. Build a DIAGxx member , it is below:
BROWSE ADCD.Z113S.PARMLIB(DIAG04) - 01.08 Line 0018 Col 001 080
/* To use this member specify DIAG=00 in SYS1.PARMLIB(IEASYSxx), */
The meaning of the volume serial number shown in the VOL field varies. For a
non-VSAM data set, it means the volume on which the data set resides. For a
VSAM data set, it means the volume on which the catalog containing the data
set entry resides.
I didn't know that before. It is quite
IBM Fault Analyzer support on z/OS.
Would anyone out there have obtained the ZAPs for the IEAVTABD version of the
module that came with the PTFs for OA38518?
I have searched under z/OS and under IBM Fault Analyzer and not found what is
needed.
Yes, I know I may have to open a PMR but
24 matches
Mail list logo
