On 2013-08-14, at 23:29, Ted MacNEIL wrote:
> I understand.
> But, that's why there are standards.
> You backed down when you shouldn't have.
>
But he had blindsided me with a fait accompli. By
the time I attempted integration and got the RENT
warning from IFOX00, he was able to argue that ther
I understand.
But, that's why there are standards.
You backed down when you shouldn't have.
My complaint is the dictatorial SYSPROG.
-
Ted MacNEIL
eamacn...@yahoo.ca
Twitter: @TedMacNEIL
-Original Message-
From: Paul Gilmartin
Sender: IBM Mainframe Discussion List
Date:
On Thu, 15 Aug 2013 03:04:35 +, Ted MacNEIL wrote:
>>are limited by their sysprogs in whatever they can or cannot do (up to the
>>point of not having any say in what compiler option they could or could not
>>use in their COBOL applications.)
>
>Their SYSPROGs have too much power!
>Applicatio
On 15/08/2013 11:04 AM, Ted MacNEIL wrote:
are limited by their sysprogs in whatever they can or cannot do (up to the
point of not having any say in what compiler option they could or could not use
in their COBOL applications.)
Their SYSPROGs have too much power!
Applications Programmers are t
>are limited by their sysprogs in whatever they can or cannot do (up to the
>point of not having any say in what compiler option they could or could not
>use in their COBOL applications.)
Their SYSPROGs have too much power!
Applications Programmers are there to facilitate the business.
So are
Paul Gilmartin said:
>You fail to appreciate how much making them UNIX directories could
>have decomplicated your life. I suspect one of the Dovetailed utilities
>could let you do a local spawn of a UNIX executable using the unneutered
>names and propagating DDNAMES. (Or perhaps BPXWUNIX if you e
John Gilmore said:
>Recall that while a PDSE member name may be at most 8 of the usual
>characters in length, an alias of such a member name may be at most
>1024 characters in length from an enlarged character set. If then you
>have a routine name R that is immediately usable as a PDSE member
>nam
On Wed, 14 Aug 2013 17:14:16 -0500, Ze'ev Atlas wrote:
>>Excellent! Making them PDSEs will decomplicate your life.
>
>No, it won't. PDSEs are fine and easier to work with then PDSs
>
>My main issues were
>
>There is no easy way to load members to a library that is defined VB, 255
>(IEBUPDTE did
The scheme you have outlined will certainly do the job. It is perhaps
more labor-intensive than it needs to be.
Recall that while a PDSE member name may be at most 8 of the usual
characters in length, an alias of such a member name may be at most
1024 characters in length from an enlarged charact
This is where I go to get end of service/end of marketing dates:
http://www-03.ibm.com/systems/z/os/zos/support/zos_eos_dates.html
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.
>Excellent! Making them PDSEs will decomplicate your life.
No, it won't. PDSEs are fine and easier to work with then PDSs
My main issues were
There is no easy way to load members to a library that is defined VB, 255
(IEBUPDTE did not work on that best). I guess I could have used individual
Excellent! Making them PDSEs will decomplicate your life.
John Gilmore, Ashland, MA 01721 - USA
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM
In <7806785360373454.wa.paulgboulderaim@listserv.ua.edu>, on
08/13/2013
at 03:47 PM, Paul Gilmartin said:
>I believe SYSPROC, SYSOUT, SYSPRINT, and SYSIN are superfluous.
They are in this case. SYSPROC and SYSEXEC are only needed if you
invoke command procedures (CLIST, REXX) from them. S
In
,
on 08/13/2013
at 07:17 PM, Peter Relson said:
>>It's surprising to me that simply routing the command causes
>>a different linklst to be used (guessing the old one).
>It should be surprising. It is not possible.
That depends on what "it" is. If the command is processed in a
different a
On Wed, 14 Aug 2013 15:57:31 -0400, John Gilmore wrote:
>It is very late in the day to introduce a new PDS as opposed to PDSE
>library of this sort.
>
It can be environmentally dictated. In our lab we have more systems
at more releases (some unsupported, but you know how customers
are) than para
>It is very late in the day to introduce a new PDS as opposed to PDSE
>library of this sort.
The loadlib and some other libraries are indeed PDSE (I used the word PDS
loosly)
ZA
--
For IBM-MAIN subscribe / signoff / archive acc
bernd wrote
>Normally, if you compile C sources you got from "somewhere" on z/OS
>using the more classical compiler options, this is no problem, unless you
>have external function names that are longer than 8 characters and that
>don't differ in their first 8 characters, and for such situations,
>
It is very late in the day to introduce a new PDS as opposed to PDSE
library of this sort.
Moreover, while PDSE members must have at most eight-character
principal names they may have long aliases.
John Gilmore, Ashland, MA 01721 - USA
Bernd wrote
>shortening the functions' names to 8, upper case characters, COBOL API, etc.
>I suggest you consider adding #pragma maps for the long function names;
>if you do this, you don't need to change nothing else.
The distribution to classic z/OS is PDS oriented and I was specifically asked
The University of Chicago will soon be posting a position for a z/OS Systems
Programmer with a minimum 10+ years of experience in CICS and ACF2 installation
and administration.
Todd Last
Team Lead, Mainframe Systems
The University of Chicago
Chicago, IL 60613
tl...@uchicago.edu
-
> In developing a new TCP/IP application I am causing our z/OS system to
crash
> and I don't know how to determine the cause. The only clue I can find
is in
> the output for the job that was running, which shows an S2F3 abend code.
> After re-IPLing, the JES console shows typical application mes
>...I'm going to make a guess that the OP is using SDSF to issue the commands
Yes, all commands were done in SDSF.
-Jim
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu w
>>It's surprising to me that simply routing the command causes
>>a different linklst to be used (guessing the old one).
>It should be surprising. It is not possible.
With all due respect and my humble thanks for your input, for the record, this
is an inaccurate blanket statement. Someone may
In developing a new TCP/IP application I am causing our z/OS system to crash
and I don't know how to determine the cause. The only clue I can find is in
the output for the job that was running, which shows an S2F3 abend code.
After re-IPLing, the JES console shows typical application messages and
ISTR that CA-RECLAIM was a z/OS 1.12 feature.
At any rate, I have been using this for DFHSM cds's and all other VSAM KSDS's
since shortly after I converted to z/OS 1.13 in 03/2012 w/no issues (I skipped
z/OS 1.12).
It seems to work as advertised, drastically reducing the frequency of CDS
re-org
Hello, we just upgraded our last lpar to zos 1.13 so now have the option
of utilizing the ca-reclaim option. As of now, it is not defined in our
parmlib so is dormant. I have both an rmm cds and an hsm bcds reorg
necessary in the upcoming months and was wondering if anyone has experience
yet wit
Thank you sir!!
Dr. Rick Williams
---Original Message---
From: Thomas Berg
Date: 8/14/2013 11:16:19 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Rexx Compile
This should work I think (simple example!):
//REXXCOMP EXEC PGM=REXXCOMP,
// PARM='SLINE(AUTO),NOCEXEC,DLINK,PRINT,SOURC
SHARE MVS Core Technologies Project Manager Mary Anne Matyaz takes a few
minutes out of her busy schedule to blog about the outstanding
conference going on here in Boston...
http://www.share.org/p/bl/et/blogid=9&blogaid=247
--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Dri
This should work I think (simple example!):
//REXXCOMP EXEC PGM=REXXCOMP,
// PARM='SLINE(AUTO),NOCEXEC,DLINK,PRINT,SOURCE,XREF'
//* =
//STEPLIB DDDISP=SHR,DSN=REXX.SFANLMD REXX COMPILER LOAD LIB
//S
I have an ETR in on this, but I have a feeling that person helping me is west
coast! I work 6am-2pm EDT and was hoping for answer today! Thought I would
seek help from all you VM experts.
While trying to apply maintenance on vm 6.2, I got the following error:
SV:VMFP2P1965E The command, CP SEN
There is a product call EDGE Profolio Analysis that supports load modules. The
product only supported modules stored in PDS's. The last time I used the
product did not support PDSE's. The product was not expensive but I do not
know the current price for the product.
Regards
Otto H Schumacher
Options in effect
--
ADV QUOTE DATA(31) NODECK NODUMP NODYNAMNOFASTSRT
LIB LIST
MAP NONUM OBJ NOOFFSET OPTIMIZE OUTDD(Supplied)
NUMPROC(NOPFD) NORENT
RES SEQ
And more importantly CBT file 321, COBANAL, which does a passable job of
extracting the COBOL options directly from the load module code.
IIRC File 330 only provides an ISPF skin for COBANAL and not COBANAL itself.
HTH
Peter
-Original Message-
From: IBM Mainframe Discussion List [mailt
I was wondering, would anyone out there have the necessary JCL required to
compile an link a rexx routine?
Thanks!
Dr. Rick Williams
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists..
File Manager has some nice loadmod functions if you have it..
Sent from my iPhone
On Aug 14, 2013, at 7:51, Elardus Engelbrecht
wrote:
> John Gilmore wrote:
>
>> What AMBLIST does, and all it does, is make IDRs (IDentification
>> Records)---They are generated by the binder in response to IDE
On Tue, 13 Aug 2013 19:17:49 -0400, Peter Relson wrote:
>Route does little more than send the command to another system. On that
>system that command may be processed by some number of system address
>spaces (such as master, consoles). Each will use whatever its lnklst is.
>
>I don't know by what
John Gilmore wrote:
>What AMBLIST does, and all it does, is make IDRs (IDentification
>Records)---They are generated by the binder in response to IDENTIFY statements
>in its input stream---available.
This I know. Whew! :-D
>If a compiler propagates information about the options that were used
What AMBLIST does, and all it does, is make IDRs (IDentification
Records)---They are generated by the binder in response to IDENTIFY
statements in its input stream---available.
If a compiler propagates information about the options that were used
in a compilation, AMBLIST makes it available. If n
I have found that the use of z/OS facilities in configuring z/TPF can
now in fact be avoided, although other, less satisfactory external
ones must be used instead.
The original context of Dr Johnson's celebrated observation---He was
comparing a woman preaching to a dog walking on its hind legs---i
John Gilmore wrote:
>Look also at the IBM utility program AMBLIST.
Unless I missed something obvious, I believe AMBLIST shows the binder
options/results of options, not COBOL compiler options.
However I know some compiler options are propagated to binder unless it is
overriden.
Perhaps could
On Wed, 14 Aug 2013 03:28:40 -0500 Victor Hugo Ochoa Avila
wrote:
:>Hello everyone.
:>A question.
:>What is the procedure to protect the MCS consoles?
:>I need to protect consoles with RACF, and allow access to a particular group
support.
CONSOLxx
DEFAULT LOGON(REQUIRED)
--
Binyamin Disse
W dniu 2013-08-14 10:28, Victor Hugo Ochoa Avila pisze:
Hello everyone.
A question.
What is the procedure to protect the MCS consoles?
I need to protect consoles with RACF, and allow access to a particular group
support.
1. Protect resources, not tools. Console is rather tool than resource.
T
Look also at the IBM utility program AMBLIST.
John Gilmore, Ashland, MA 01721 - USA
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Hello everyone.
A question.
What is the procedure to protect the MCS consoles?
I need to protect consoles with RACF, and allow access to a particular group
support.
Thanks and regards
ATTE
Victor Avila
--
For IBM-MAIN subscrib
Dump and restore.
On Wed, Aug 14, 2013 at 1:51 PM, Gibney, Dave wrote:
> I wouldn't think that would be required or all that useful. What method
> did you choose to use for the reorg?
>
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> >
see file 330 on cbttape.org.
ITschak
On Wed, Aug 14, 2013 at 10:52 AM, Ron Thomas wrote:
> Hello. From the load module i need to get all compiler options that is
> used to build the code(cobol.db2). Pls some one let us know is there any
> standard routines to get this information?
>
>
> Thank
I wouldn't think that would be required or all that useful. What method did you
choose to use for the reorg?
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of mf db
> Sent: Wednesday, August 14, 2013 1:12 AM
> To: IBM-MAIN@LISTSERV
Thanks all for your opinions and great suggestions. The environment is like
Intended usercat is connected to all the Mastercatalog. So after the
CATALOG rebuild, a F CATALOG,RESTART would be a good choice to refresh the
entries ?
On Wed, Aug 14, 2013 at 3:33 AM, Tom Marchant wrote:
> On Tue, 13
Hello. From the load module i need to get all compiler options that is used to
build the code(cobol.db2). Pls some one let us know is there any standard
routines to get this information?
Thanks,
Ron T
--
For IBM-MAIN subscrib
49 matches
Mail list logo
