System 04E abend bringing up DB2 CONTROL ADDRESS SPACE

I have been getting system 04E abends trying to bring up the DB2 Control Address Space The following link http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/dsnc1k16/9.0?ACTI ON=MATCHES

Re: Dumb question on DEFINE ALIAS

Comments in context below... -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of R.S. Sent: Sunday, July 11, 2010 4:17 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Dumb question on DEFINE ALIAS W dniu 2010-07-11 22:41, Tony @ Comcast pisze: >

Re: Dumb question on DEFINE ALIAS

I thought it was a "good" thing at the time because it was. We churned out lots of work at minimal cost to our employer and it was bulletproof. The track record proved it out as we made a business case to forestall a mainframe replacement for several years through the madness of Y2K. Our little

Re: instream data

On Mon, 12 Jul 2010 10:03:58 +1000, Clement Clarke wrote: >> >For over 40 years, Jol has allowed you to do just that. > >Jol is a free format JCL replacement language, loosely based on PL/I. > >You can declare Data Sets and Programs, and use commands such as Run (a >program) or Copy a data set and

Re: instream data

Frank Swarbrick wrote: Now that we've been on z/OS for a few weeks I feel to need to ask a question that has annoyed me since I started working on z/OS two years ago. Instream datasets are good. Why are they not supported inside of procs? Is there a technical reason, or is it just "because"

Re: JES2 Exit 53 problem

Doesn't reg 0 point to the XPL ??? -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Mark Yuhas Sent: Saturday, July 10, 2010 11:43 PM To: IBM-MAIN@bama.ua.edu Subject: JES2 Exit 53 problem Maybe another set of eyes can show me the error of

Re: Dumb question on DEFINE ALIAS

I don't understand why you think this a good thing! It' not. Aliases en masse is NOT a problem! It reduces clutter, and makes a storage analyst's job a heck of a lot easier! - I'm a SuperHero with neither powers, nor motivation! Kimota! -Original Message- From: "Tony @ Comcast" Sender: I

Re: Dumb question on DEFINE ALIAS

W dniu 2010-07-11 22:41, Tony @ Comcast pisze: Years ago I worked for a small MVS shop that functioned quite well using the "catalog name being the same as the hlq" trick to avoid the need for creating aliases en masse. It was handy for the TSO user population to have a catalog called ISPF, the

Re: Amusing JCL Oddity

In <4c332ecc.90...@acm.org>, on 07/06/2010 at 08:25 AM, "Joel C. Ewing" said: >This would be a semantic error (dealing with meaning), No, it would be a syntax error that is easier to catch with a semantic constraint than with classical parsing techniques. Do not confuse "grammar" with, e.g.,

Re: Backup/Restore products at z/OS sites

In , on 07/06/2010 at 09:49 PM, Dan Squillace said: >I never did say why I was asking. In SAS 9.2, we already support >z/OS software distribution via FTP, Then why do you require your customers to use the Download Manager and a proxy server for electronic delivery? Your installation document

Re: Dumb question on DEFINE ALIAS

Years ago I worked for a small MVS shop that functioned quite well using the "catalog name being the same as the hlq" trick to avoid the need for creating aliases en masse. It was handy for the TSO user population to have a catalog called ISPF, the prefixing everyone's personal datasets accordingl

Re: Amusing JCL Oddity

In <45e5f2f45d7878458ee5ca6796973355213...@usdaexch01.kbm1.loc>, on 07/06/2010 at 08:22 AM, "Staller, Allan" said: >Again, what is syntactically incorrect? Duplicate keywords. >Everything after PROC=A# is a parameter or nullification (V=) passed >to the procedure. "SP1=3000" is not passed t

Re: Amusing JCL Oddity

In <45e5f2f45d7878458ee5ca6796973355213...@usdaexch01.kbm1.loc>, on 07/06/2010 at 07:27 AM, "Staller, Allan" said: >Why? What is syntactically incorrect with the below? The duplicate keywords. >Without observing the procedure being called, it is impossible to >determine if a syntax error is