Ron,
glad you got it working.
I did ask you to do a query link a few posts ago, but I think you maybe missed
it? Never mind, all's well that ends well..
Vince.
--
For IBM-MAIN subscribe / signoff / archive access
Vince,
We were able to get this issue resolved. IBM support had me issue a QUERY LINK
on my z/VM side and noticed that the LINK was in a hold status. They then had
me issue a FREE LINK command and after starting the transmitters on the z/OS
side everything started working. Not sure how the
Thanks Vince,
I will be sure to post the resolution for this once we get it resolved.
Thanks,
Ron McCabe
Manager of Mainframe/Midrange Systems
Mutual of Enumclaw
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Vince Getgood
Sent: Wednesday, February 13, 2019 12:16
Ron,
I'm afraid this has now gone outside my area of expertise...
From what IBM say it's z/VM that's caused the connection to close, which
suggests that the output on the z/OS side is ok.
Sorry I can't be of any more help. It would be useful to know what the outcome
is though.
Vince,
The NETSTAT ALLC command does not show anything on port 3603. I have very
little in my display which is what I would expect...
User Id ConnLocal SocketForeign Socket State
-- - ----- -- -
FTPSERVE 1001
Ron,
If JES is saying the networking is started, that suggests that the connection
between JES and z/VM is good.
Your PROFILE TCPIP might tell you what's on port 3603, but the z/VM TCPIP
command NETSTAT ALLC should display the connection.
If the nje connection is starting, then you should be
Vince,
I do not know what is on port 3603 on z/VM and I don't know how to find out
what is there. I got the Query NODE/LINE commands to work after you pointed
out that they are RSCS commands...I kept trying to run them from TCPMAINT.
When I start the LINK from z/VM and then very quickly start
Ron,
You have an established session from JES's Netserv to z/VM -
EZZ2587I JES2S001 7D6F 10.100.5.71..175 10.100.5.73..3603
Establsh
(What's at port 3603 on z/VM btw?)
Your start link looks successful, both on z/VM & z/OS - that seems to suggest
that the network is ok.
The
Vince,
I do appreciate the help even though there is about an 8 hour time difference
as I am on the West Coast.
Yes, we do have 2 connections from our z/OS LPAR (10.100.5.71)...First
connection is to 10.100.5.72 which is another z/OS LPAR where we do our backups
and that connection is working
Ron,
Your PORT statement should be fine. It's recommended in the z/VM manual.
The NETSTAT ALLCONN display shows that JES's NETSRV is listening (waiting for a
connection from another TCP/IP) on port 175.
It also shows two established connections -
one JES NETSRV connection between 10.100.5.71
Forgot to mention that once I added port 175 to my authorized port list in my
TCPIP PROFILE on z/VM I no longer get an error.
Thanks,
Ron McCabe
Manager of Mainframe/Midrange Systems
Mutual of Enumclaw
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
McCabe, Ron
Vince,
Here is the results of the TSO command NETSTAT ALLCONN (PORT 175
EZZ2350I MVS TCP/IP NETSTAT CS V2R2 TCPIP Name: TCPIP 08:32:32
EZZ2585I User Id Conn Local Socket Foreign Socket State
EZZ2586I --- --
Ron,
You don't need a separate FICON port for a FICON CTC (FCTC). Any FICON port
that is shared between the LPARS can be used. FCTC would just be another LCU
on that port.
However, all the examples and diagrams about FCTC in the FICON manuals describe
using a switch - that's simply not
Yes, all necessary RSCS resources are available/started...if not I would have
hoped IBM Support would have said something.
Yes, there is a process listening on port 175 on the z/VM side.
I get a connection using telnet to port 175 but then it fails very soon after
which I assume is because
IAZ0545I NETSRV1 Error encountered in function connect() - EDC8128I
Connection refused.
IAZ0543I NETSRV1 TCP/IP connection with IP Addr: 10.100.5.73 Port: 175
ended due to TCP/IP error, rc: 1128
The "connection refused" error can indicate a lack of resources on the
Vince,
Thanks for letting me know about using a FICON CTC...the problem was when we
ordered the z13s we didn't order enough FICON adapters...guess our research was
not through enough.
As far as where the problem actually is...I believe it is the network to but
I'm losing that battle and it is
Dana,
From what I remember, no switch is required. I believe any FICON port will do.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Ron,
Look at Output Disposition in the IBM Knowledge Center.
See
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieab600/iea3b6_Subparameter_definitions1.htm
You might have an output disposition of KEEP or LEAVE. You can change
these with SDSF and release the job so it
On Wed, 6 Feb 2019 03:14:51 -0600, Vince Getgood wrote:
>Ron,
>AFAIK, you are correct regarding a virtual CTC, but you can still define a
>real FICON CTC - I think I'm correct in saying you just need one spare FICON
>port, unlike ESCON, where you needed two, and a cable between them.
>
We
Ron,
AFAIK, you are correct regarding a virtual CTC, but you can still define a real
FICON CTC - I think I'm correct in saying you just need one spare FICON port,
unlike ESCON, where you needed two, and a cable between them.
Assuming nothing has changed on the mainframe, and you are running
Paul Gilmartin wrote, in part:
>Good idea. But why not start each of your responses on a new line? And
>distingush original text by ">" quotation marks or indention? Does not
>MS-Exchange, which appears to be your mailer, support such things?
A nit, Gil: Exchange is an MTA, not an MUA.
On Tue, 5 Feb 2019 17:10:52 +, McCabe, Ron wrote:
>
>I found it easier to put my responses below after each of your questions.
>
Good idea. But why not start each of your responses on a new line? And
distingush original text by ">" quotation marks or indention? Does not
MS-Exchange, which
Vince,
I found it easier to put my responses below after each of your questions.
Thanks,
Ron McCabe
Mutual of Enumclaw
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Vince Getgood
Sent: Tuesday, February 05, 2019 1:41 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re:
Ron,
Forgive me, but it sounds like you are a little out of your depth with this.
Z13 doesn't allow a CTC? Since when? AFAIK, you can have a FICON CTC on ANY
z hardware.
"TCPNJE has been working for nearly 3 years and then all of a sudden it isn't
and networking says it's a mainframe
Have you checked the selection criteria? The status of each of the pieces? My
guess is that something isn't active.
Of course, it could be a firewall issue, but check that everything is working
on the JES2 side before looking at that.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
Hello listers,
I'm still working this issue and just to let you all know my networking
expertise is NIL and I'm still in a learning process as far as z/OS systems
programming goes, our systems programmer, who I was learning from, retired last
November and I got the privilege (if that is what
David,
My comments are inaccurate in the example...
OOPS
On Mon, Feb 4, 2019 at 1:16 PM Wayne Bickerdike wrote:
>
> Hi Wayne,
> Instead of "ISFEXEC ST", I would've used "ISFEXEC DA OJOB" or ISFEXEC
> "DA OSTC" (depending upon whether CICS is a Job or Started Task).
> The reason is that ST
Hi Wayne,
Instead of "ISFEXEC ST", I would've used "ISFEXEC DA OJOB" or ISFEXEC
"DA OSTC" (depending upon whether CICS is a Job or Started Task).
The reason is that ST shows running Jobs/STCs and already ended Job/STCs
(that haven't been Purged).
Regards,
David
I want all jobs, running or not.
Hi Wayne,
Instead of "ISFEXEC ST", I would've used "ISFEXEC DA OJOB" or ISFEXEC
"DA OSTC" (depending upon whether CICS is a Job or Started Task).
The reason is that ST shows running Jobs/STCs and already ended Job/STCs
(that haven't been Purged).
Regards,
David
On 2019-02-03 19:20, Wayne
Here's how I've pulled the CEEMSG dataset and parsed it for abends. Adjust
SYSOUT names to suit.
ARG IPARM
rc=isfcalls('ON')
CICS_REGION = STRIP(IPARM)
/* SET UP JOB CARD AND JCL FOR REMOTE SPUFI EXECUTION */
CALL JOBSET
/* Access the ST display */
isfprefix = IPARM
Address SDSF "ISFEXEC
RGEN has plenty of examples. From SDSF command line, RGEN X and roll your
own.
On Mon, Feb 4, 2019 at 10:03 AM Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> On Sun, 3 Feb 2019 20:21:23 +, Seymour J Metz wrote:
>
> >Well, there's always XDC, but the basic answer
On Sun, 3 Feb 2019 20:21:23 +, Seymour J Metz wrote:
>Well, there's always XDC, but the basic answer is that it depends on how the
>output datasets were defined.
>
I've had success using the Rexx interface to SDSF, which allocates a generated
DDNAME
to the SYSOUT. I can use alternate DD
, 2019 2:07 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: How can I get reports in the Output Queue in SDSF to print
Hello,
How can I get reports that are in the Output Queue in SDSF to be
re-printed...basically I want them to be processed again.
Thanks,
Ron McCabe
Manager of Mainframe/Midrange
?
Lizette
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of
> McCabe, Ron
> Sent: Friday, February 01, 2019 12:07 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: How can I get reports in the Output Queue in SDSF to print
>
> Hello,
&g
Ron,
If they are in the output queue, then they probably haven't been printed.
Do you want to keep a copy on the output queue?
If not, just change the class and destination to one that a printer processes.
If you want the output copy left, you could do something like XDC it to a flat
file,
Hello,
How can I get reports that are in the Output Queue in SDSF to be
re-printed...basically I want them to be processed again.
Thanks,
Ron McCabe
Manager of Mainframe/Midrange Systems
Mutual of Enumclaw
Confidentiality Notice: This e- mail and all attachments may contain
CONFIDENTIAL
36 matches
Mail list logo
