We kept a 120 MIP system on "hospice" for several years starting with 4 FTE and
dwindling down to 1.5 FTE. Even a doomed system required 2 hardware upgrades,
several OS versions, encryption for TN3270, distributed printing, internet data
transfer and general hand holding.
Len Rugen
Hi Elardus - Thanks very much for your support.
I was specifically looking at effort / man hours estimate for supporting
standard z/OS MF infrastructure which does not include H/W support.
Basically wanted to
how many FTEs does the industry standard recommend for no of LPARs. etc.,
for DB2
(Posting for a co-worker)
We have installed TSSO (PRE Z1 .8 version) Our test:
DIPLINF TABENTRY MSG=IEE254I,ACTION=OSCMD,MATCHLIM=17,ECHO=YES, X
TEXT='D A,L'
IEE254I is the message response from a D IPLINFO.
When we issue D IPLINFO and the message fires...
TSSO rapidly
On Tue, 13 Feb 2018 20:00:47 -0600, Jim Ruddy wrote:
>Wouldn't a 64K byte parameter list run into problems with programs such as
>HLASM, compilers, and other programs which allow an optional DD name list to
>be passed as a second parameter when invoked from a program? As I recall, they
>detect
Nevermind - wrong bit - been too long and too long of a day. Sorry.
Jim
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Wouldn't a 64K byte parameter list run into problems with programs such as
HLASM, compilers, and other programs which allow an optional DD name list to be
passed as a second parameter when invoked from a program? As I recall, they
detect whether the DD name list is passed by testing the high
On Tue, 13 Feb 2018 17:46:28 -0800, Charles Mills wrote:
>And no real reason a program could not support 64ki-1 bytes. Not looking at
>the specs for "standard linkage" but there is no real good reason to treat the
>length as signed.
>
Tradition? ("real good reason"?)
A while ago, I
Hello,
I am not sure if it is possible using TBDISPL service. I am able to do that
using dynamic area in panels. Of course, more work, more controls...
Dan
Sent from Yahoo Mail for iPhone
On Monday, February 12, 2018, 3:39 PM, ITschak Mugzach
wrote:
Tried that. it does
And no real reason a program could not support 64ki-1 bytes. Not looking at the
specs for "standard linkage" but there is no real good reason to treat the
length as signed.
Beyond that would require a significant change in the linkage.
Charles
-Original Message-
From: IBM Mainframe
On Tue, 6 Feb 2018 10:49:38 -0800, Tom Ross wrote:
>IBM COBOL development needs your help!
>
>We are reviewing a request to change our support for OPTFILE and SYSOPTF
>to allow usage of DD SYSOPTF without the compiler option OPTFILE.
>
>For background, this is where
Today, during a 'back when' discussion, this came up.
Back in '81, during my last year in college (Management Information
Science they called it then), the advanced students 'played' with a
training database written in Fortran. We had the source, compiled it,
and added features.
One of the
Thank you very much for all your help
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Hi Anne,
Redirect might sound like administration, but I know Infoprint Central can
display the printer definitions from the inventory but it does not edit
them. You need Administrator authority to change the printer definitions
either with the ISPF panels or with the pidu command in OMVS. The
On Wed, 14 Feb 2018 00:00:10 +, Farley, Peter x23353 wrote:
>
>PMFJI here but the limit with PARMDD is 32K I believe. JES/JCL limit is 100,
>not 255. The COBOL questions is, does the compiler correctly process PARMDD
>input > 255 characters, and if so which version(s)? Only V5+? I could
Tom,
PMFJI here but the limit with PARMDD is 32K I believe. JES/JCL limit is 100,
not 255. The COBOL questions is, does the compiler correctly process PARMDD
input > 255 characters, and if so which version(s)? Only V5+? I could
understand V4 not supporting it, but not V5+.
Peter
We added OPTFILE as a response to customer request, I believe it was
well before PARMDD, but not positive.
Someone else asked what the COMPILER limit for reading the PARM=
options string is, but there is none. There is a JCL/JES limit of
255 bytes. There is no limit for SYSOPTF (using OPTFILE).
I thought that if PTF A was superseded by B, and B superseded by C, then SMPE
would only install only C and mark A and B as SUP'D. That logic, if it obtains,
always made sense to me.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program
On 2/13/2018 5:23 PM, Jesse 1 Robinson wrote:
This schema looks good, but I don't understand how '/SERVICE/' alone can handle
more than one z/OS release concurrently. We use '/OSRxx/' where xx represents
the version/release such as 12, 13, 21, 23. That way any number of releases can
be
On Tue, 13 Feb 2018 16:52:06 -0600, Matthew Stitt wrote:
>With WAS, I've encountered certain PTFs (fixpacks) which supersede other ones
>and create errors like this when both (or more) fixpacks are being applied at
>once. The solution I've found is to apply each fixpack separately.
>
That
With WAS, I've encountered certain PTFs (fixpacks) which supersede other ones
and create errors like this when both (or more) fixpacks are being applied at
once. The solution I've found is to apply each fixpack separately.
HTH
Matthew
On Tue, 13 Feb 2018 10:13:18 -0500, John Eells
This schema looks good, but I don't understand how '/SERVICE/' alone can handle
more than one z/OS release concurrently. We use '/OSRxx/' where xx represents
the version/release such as 12, 13, 21, 23. That way any number of releases can
be managed and *distinguished* concurrently. This has
TCBFSA is 0 when SVAREA=NO is specified on ATTACH.
TCBFSA points to above-the-line storage for key 9 TCBs
Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp.
Poughkeepsie NY
IBM Mainframe Discussion List wrote on
02/13/2018 04:07:10 AM:
> From: Steff
There are some configuration mis-matches that could cause the Autologon
to fail. As already mentioned, an incorrect LUNAME could cause this, also an
incorrect password (if you are using them). I recall some vendor type RJE
device that never successfully signed on with the JES2
There is a chance that no one remembers :-)
Is the LU active? Is the luname correct?
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Lizette Koehler
Sent: Tuesday, February 13, 2018 1:43 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject:
I guess no one remembers JES2 Remotes or can answer this very simple question
Lizette
;-D
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Lizette Koehler
> Sent: Monday, February 12, 2018 4:47 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
My main worry about using WHILECATALOG is that there was an old practice
were some tapes were manually set in CA-1 to have extended retention
periods because of something that happened 'special' the day they were
created.
On the other hand, all the people that used to know the why those
RMM was designed around the assumption that tape datasets would be cataloged or
else scratched. When we converted to it many years ago, we had to deal with a
wholly different business practice: keep tape data sets, including 'GDG
members', more or less forever. In the early days we had to
On 13 February 2018 at 07:44, Steff Gladstone wrote:
> Or you could check if R14 is pointing to a SVC 3 instruction.
That may or may not work. If you are running under TSO TEST it will
point to an SVC 97 instead.
> Actually the routine (not written by me) was using
On 2/13/2018 9:24 AM, Tony Thigpen wrote:
Thanks Tom.
Yes, I did mean VRS.
No, IBM did not do the conversion.
The output shows:
Exit status:
EDGUX100 = NONE
Are you suggesting that I not use EDGUX100, but instead use:
RMM ADDVRS DSNAME(’**’) WHILECATALOG
Will this affect all existing
The first save area must be below the line.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@listserv.ua.edu] on behalf of
Steff Gladstone [steff.gladst...@gmail.com]
Sent: Tuesday, February 13, 2018
Did you open a PMR?
Please do, if not; and, please post the PMR number.
Peter wrote:
This time again it failed
BPXF140E RETURN CODE 0090, REASON CODE 0549010C. A LINK FAILED FOR
LINK NAME /usr/lpp/InstallationManagerRepository/HBBO850/IBM
/../bbodrmak.
--
John Eells
IBM Poughkeepsie
I am pleased to invite you to a GSE Large Systems Working Group event. The
event will be a virtual event via WebEx on the 21st February 2018 from 15:00 –
16:15 GMT.
The event will contain a 1 hour session presented by Martin Packer and Anna
Shugol from IBM on “IBM zHyperlinks: new low latency
Yes... I've had the pleasure of working on many dumps with above-the-bar
storage. Pro-tip: you use ! instead of ? to jump to an 8-byte address in
IPCS Browse (or XDC, if that's your thing).
I've avoided SYSUDUMP for years... they seem to be set up to print only
what I don't need to see; besides
Thanks Tom.
Yes, I did mean VRS.
No, IBM did not do the conversion.
The output shows:
Exit status:
EDGUX100 = NONE
Are you suggesting that I not use EDGUX100, but instead use:
RMM ADDVRS DSNAME(’**’) WHILECATALOG
Will this affect all existing volumes? Is there a way to see the effect
Hi folks,
As the title says Colesoft is looking to hire an additional developer. The full
job posting can be found here: http://www.colesoft.com/careers/
Please contact us off list with questions.
Thanks
Calin Cole
--
For
On Sat, 10 Feb 2018 07:57:01 -0500, Peter Relson wrote:
>>Will the Segment created by IARV64 be visable in a dump
>>when the program issues ABEND ,DUMP,STEP
>
>A true z/OS answer: it depends.
>
>For SYSABEND/SYSUDUMP: no.
>For SYSMDUMP, I think, yes.
>
>There is no support for 64-bit
On Fri, 9 Feb 2018 04:46:33 +, Craig Pace wrote:
>I always kept a SERVICE copy of the filesystems that were IBM related and then
>applied and that is what SMP/E pointed to. Each shop usually has what works
>best for them, but below are the two main ways that I have done it.
>
>1) Less
On 2/13/2018 8:57 AM, Jake Anderson wrote:
Hi
Does anyone have a sample copy of ISPFCL ?
Jake
Jake,
From my Dynamic ISPF session:
/* Rexx */
/* trace i */
msgsave = msg()
x = msg('OFF')
address tso "ALLOC FI(ISPPROF) DA('"userid()".ISPF.ISPPROF') OLD"
if rc <> 0 then
do
profdsn =
On 2/13/2018 8:19 AM, Tony Thigpen wrote:
We recently converted from CA-1 to RMM.
I am having an issue with some tape volumes containing GDGs not
scratching after x days.
I have determined it is due to EXPDT=99000, and I am now waiting for the
person who performed the conversion to let me
Hi
Does anyone have a sample copy of ISPFCL ?
Jake
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Thanks Roger,
Still a little confused though. Upon looking at (SA38-0693-00) Infoprint Server
Operation and Administraion, Using Infoprint Central, Work with Printers, IP
PrintWay printers. (I can) start, stop, and redirect ... which does appear to
be an admin function. Again, the change does
We recently converted from CA-1 to RMM.
I am having an issue with some tape volumes containing GDGs not
scratching after x days.
I have determined it is due to EXPDT=99000, and I am now waiting for the
person who performed the conversion to let me know if the EDGUX100 exit
is installed and
Using R13 can be an issue if the linkage stack is used instead of the save area.
Dennis Roach, CISSP
AIG
Identity & Access Management | Technology Services
2929 Allen Parkway, America Building, 3rd Floor | Houston, TX 77019
Phone: 713-591-1059 (cell)
dennis.ro...@aig.com | www.aig.com
Or you could check if R14 is pointing to a SVC 3 instruction.
Actually the routine (not written by me) was using the FSA to retrieve the
pointer to the value of the PARM= parameter (saved R1).
Presumably that's a valid use as well.
It would make sense if the FSA is always below the line.
This time again it failed
BPXF140E RETURN CODE 0090, REASON CODE 0549010C. A LINK FAILED FOR
LINK NAME /usr/lpp/InstallationManagerRepository/HBBO850/IBM
/../bbodrmak.
*Reason Code : 0549010C*
BPXFSLNK 03/10/11
JRLnkAcrossFilesets: The service tried to link across file
systems
Action:
Hi,
IMO, the first save area should always be below the line.
It is provided by the operating system so that the main program of the
called application (EXEC PGM=...) can store the registers on call there.
And the first program may be AMODE 24 :-)
On the other hand, I would never use TCBFSA to
Hi,
I am in the process of converting several routines to AMODE=31 RMODE=ANY.
One of them references the address of the first problem program save area
found in the TCB.
The field is defined as follows:
TCBFSA DS0A -ADDRESS OF THE FIRST PROBLEM PROGRAM SAVE AREA
DS
47 matches
Mail list logo