Some of the ratings were unusual
Is Not very important less important than Not important ?
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Iris Rivera
Sent: 14 July 2015 20:09
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: IBM z/OS Product
Sharon,
In addition to the products others have mentioned, also consider EKC's products
- www.ekcinc.com
Regards, Bob
Robert S. Hansel
Lead RACF Specialist
RSH Consulting, Inc.
617-969-8211
www.linkedin.com/in/roberthansel
http://twitter.com/RSH_RACF
www.rshconsulting.com
In 9918895732815903.wa.antonioandrew92gmail@listserv.ua.edu, on
07/13/2015
at 10:38 AM, Antonio Andrew antonioandre...@gmail.com said:
Yes the E-mails are going through SMTP.
Do you mean WRITING TO SYSOUT=(*,SMTP)?
The product being used is IEBGENR.
That just copies your message to
In
of058a7224.5d2175d2-onc1257e83.00215232-c1257e83.00216...@se.ibm.com,
on 07/15/2015
at 08:04 AM, Steve Coalbran coal...@se.ibm.com said:
Can you be more specific.
Yes.
I tried... TSO GTTERM
GTTERM is a macro, not a command.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO
IT depends.
How do you change the configuration?
Do you have to cycle the STC?
Do you have to refresh something?
Did you do it on all systems that the PDS/E is being used?
Lizette
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
On Behalf Of
In
7006637956401197.wa.elardus.engelbrechtsita.co...@listserv.ua.edu,
on 07/13/2015
at 10:19 AM, Elardus Engelbrecht elardus.engelbre...@sita.co.za
said:
Perhaps, but, Shmuel, what will YOU do if you are in the same
position which John is talking?
What position? Or didn't you catch that
Get a back-up copy from the good SYSPLEX. Stop sharing it across SYSPLEX.
(Unless you don't update from anywhere between IPLS :) )
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
On Behalf Of Jake Anderson
Sent: Wednesday, July 15, 2015 8:40
GTTERM is an assembler macro for use in your own program.
On Jul 15, 2015 01:05, Steve Coalbran coal...@se.ibm.com wrote:
Thanks.
Can you be more specific.
I tried... TSO GTTERM and
COMMAND GTTERM NOT FOUND
***
From: Shmuel Metz (Seymour J.) shmuel+ibm-m...@patriot.net
To:
Lizette Koehler wrote:
I have not received emails in a bit, so I thought I would just check and make
sure things are going through.
Two reasons why IBM-MAIM is so silent these days:
1. July 14 is the day when Hagar the Horrible is taking his Yearly Bath. One
time in the summer, fewer in the
Think I just searched 'IBM SNA GTTERM'
Lots of hits.
Maybe most educational:
www.prycroft6.com.au/misc/3270eds.html
In a message dated 7/15/2015 5:14:13 A.M. Central Daylight Time,
john.archie.mck...@gmail.com writes:
GTTERM is an assembler macro for use in your own program.
On Jul
Hi
The dataset has a member which has all configuration Parms for a running STC
This was updated when STC was up and running
So This could be a reason for a possible corruption ?
On Wednesday 15 July 2015, Lizette Koehler stars...@mindspring.com wrote:
And basically if you are only using
Look into the fact that you can't share PDSE's across SYSPLEX's.
-
-teD
-
Original Message
From: Jake Anderson
Sent: Wednesday, July 15, 2015 17:31
To: IBM-MAIN@LISTSERV.UA.EDU
Reply To: IBM Mainframe Discussion List
Subject: Corrupt PDSE
Hello,
I get below message when i try to access a
My group is currently looking for an individual or organization that can
provide coding expertise for an HLASM coding project.
The project is to convert some HLASM programs that currently use XCF for
communications between LPARs to using TCP/IP for the same communications. All
other processing
My group is currently looking for an individual or organization that can
provide coding expertise for an HLASM coding project.
The project is to convert some HLASM programs that currently use XCF for
communications between LPARs to using TCP/IP for the same communications. All
other
Thanks.
Can you be more specific.
I tried... TSO GTTERM and
COMMAND GTTERM NOT FOUND
***
From: Shmuel Metz (Seymour J.) shmuel+ibm-m...@patriot.net
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 2015-06-14 23:16
Subject:Re: ISPF Workstation Setup ( Was: IND$FILE Resource Log
It's possible to get away with inter-sysplex PDSE sharing for such a long time
that people forget that it's verboten. I'm told that ISV serialization products
like MIM do not solve this problem.
BTW this is a common inhibitor to COBOL V5, which requires PDSE for load
modules. Many shops have
I wondered about that also. Given the layout on the screen I assumed so. Not
very clear communication for a technical communication project ...
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Ray Pearce
Sent: Wednesday, July
Hello,
I get below message when i try to access a PDSE dataset, but when I try to
access the same Dataset from a different SYSPLEX it opens up. We do share
the Dasd .
IGW702I PDSE Directory Validation Unsuccessful
DESC:ND Structure is corrupted
LTK:
PDSE's *CANNOT* be shared across SYSPLEX Boundaries.
PDSE's *CAN* be shared within a SYSPLEX if the SMSPDSE* address spaces are
running...
HTH,
snip
I get below message when i try to access a PDSE dataset, but when I try to
access the same Dataset from a different SYSPLEX it opens up. We do
Set ibm-main mail
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Ibm Info on corrupted PDSEs:
http://www-01.ibm.com/support/docview.wss?uid=isg1II14252
On Wed, Jul 15, 2015 at 11:39 AM, Jake Anderson justmainfra...@gmail.com
wrote:
Hello,
I get below message when i try to access a PDSE dataset, but when I try to
access the same Dataset from a different
21 matches
Mail list logo
