Discussion:
TCPIP ERROR - OS/390 2.10 NFSC "badXid" Help Please
(too old to reply)
puck64au
2008-03-15 07:36:45 UTC
Permalink
Hi All,
TCPIP Seems to Fail at IPL with the following message at the console -

" 00- 16.14.52 STC00006 GFSC099I (D) CTMRD 11 TMRD :
00000003:TmrD
- pidTmr(00010012) badXid"

STC00006 equates to NFSC ---> NFSC STC00006 NFSC ,
15,EXECUTION

I can connect to OS390 via 127.0.0.1 port 3270 :-)

I can Ping OS390 (192.168.0.4) from the host machine (192.168.0.2)and
reverse, but I cannot connect from WinXP via FTP Port 21 or use port
23
for TSO Connections (HostExplorer v6)

Steps taken to fix/check..
1 deleted ths shadow files (places me back as far as August 2005)
IPL'd
with the same result
deleted the shadow files reloaded a ghost image WinXP dated Aug 2007
IPL'd with the same result
Deleted the shadow files again replaced Herc with an old copy that
worked (July 2007) IPL'd again Same result.

Can someone help?

I have the following from the IPL..Herclog.txt, HTTPD1.TXT, NFSC.TXT,
NFSS.TXT, PORTMAP.TXT, STC00006.TXT, SYSLOG.TXT, TCPIP.TXT and
VTAM.TXT

Please Reply here or via E-Mail to puck64au AT yahoo dot com

CONSOLE
*16.12.31 STC00003 *????????? ?????? PRODUCTCODE
xxxxxxxxxxxxxxxxxxxx
* HAS EXPIRED
- 16.14.11 STC00005 VTAMAP96I 000 record(s) contained errors.
- 16.14.11 STC00005 VTAMAP97I 015 internal command(s) executed.
- 16.14.11 STC00005 VTAMAP98I 008 system command(s) issued.
- 16.14.11 STC00005 VTAMAP99I Execution completed.
- 16.14.11 STC00005 IEF404I VTAMAPPL - ENDED - TIME=16.14.11
- 16.14.11 STC00026 $HASP373 HTTPD1 STARTED
- 16.14.11 STC00027 $HASP373 NFSS STARTED
- 16.14.11 STC00026 IMW3534I PID: 16842763 SERVER STARTING
- 16.14.13 STC00027 GFSA348I OS/390 NETWORK FILE SYSTEM SERVER
(HDZ11TS)
- STARTED.
- 16.14.16 STC00026 IMW3536I SA 16842763 0.0.0.0:80 * * READY
00- 16.14.52 STC00006 GFSC099I (D) CTMRD 11 TMRD :
00000003:TmrD
- pidTmr(00010012) badXid
- 16.14.52 STC00006 GFSC729W OS/390 NFS CLIENT IS UNABLE TO
RESERVE 384
- SOCKETS, CURRENT MAXFILEPROC IS 256
- 16.14.52 STC00006 GFSC700I OS/390 NETWORK FILE SYSTEM CLIENT
(HDZ11TC)
- STARTED

IEE612I CN=01 DEVNUM=0700 SYS=P390


IEE163I MODE= RD
======================================================================
==
================
CONFIG TCPIP INFO
0E20 3088 CTCI-W32 192.168.0.4 192.168.0.2 1024 64
0E21 3088 CTCI-W32 192.168.0.4 192.168.0.2 1024 64

HERCULES LOG
16:11:14 Hercules Version 3.05-pre-cvshead-msvc-20071023
16:11:14 (c)Copyright 1999-2007 by Roger Bowler, Jan Jaeger, and
others
16:11:14 Built on Oct 23 2007 at 19:10:50
16:11:14 Build information:
16:11:14 Win32 (MSVC) build
16:11:14 Modes: S/370 ESA/390 z/Arch
16:11:14 Max CPU Engines: 8
16:11:14 Using fthreads instead of pthreads
16:11:14 Dynamic loading support
16:11:14 Loadable module default base directory is .
16:11:14 Using shared libraries
16:11:14 HTTP Server support
16:11:14 No SIGABEND handler
16:11:14 Regular Expressions support
16:11:14 Automatic Operator support
16:11:14 Machine dependent assists: cmpxchg1 cmpxchg4 cmpxchg8
fetch_dw store_dw
16:11:14 Running on GEMINI Windows_NT-5.1 i686 MP=2
16:11:14 Crypto module loaded (c) Copyright Bernard van der Helm,
2003-
2007
16:11:14 Active: Message Security Assist
16:11:14 Message Security Assist Extension 1
16:11:14 HHCCF065I Hercules: tid=00000644, pid=2184, pgid=2184,
priority=0
16:11:14 HHCTE001I Console connection thread started: tid=00000518,
pid=2184
1
16:11:14 F:\Hercules\TunTap32.dll version 2.1.0.404 initiated
16:11:14 HHCCT073I 0E20: TUN device tun0 opened
16:11:14
16:11:14 HHCCF039W PGMPRDOS LICENSED specified.
16:11:14 Licensed program product operating systems are
enabled.
16:11:14 You are responsible for meeting all conditions of
your
16:11:14 software license.
16:11:14
16:11:14 HHCCF069I Run-options enabled for this run:
16:11:14 NUMCPU: 2
16:11:14 ASN-and-LX-reuse: DISabled
16:11:14 DIAG8CMD: DISabled
16:11:14 HHCCP002I CPU0000 thread started: tid=00000B08, pid=2184,
priority=15
16:11:14 HHCCP003I CPU0000 architecture mode ESA/390
16:11:14 HHCTT002I Timer thread started: tid=00000B14, pid=2184,
priority=0
16:11:14 HHCCP002I CPU0001 thread started: tid=00000A68, pid=2184,
priority=15
16:11:14 HHCCP003I CPU0001 architecture mode ESA/390
16:11:14 HHCPN001I Control panel thread started: tid=00000644,
pid=2184
16:11:14 HHCHT001I HTTP listener thread started: tid=00000954,
pid=2184
16:11:14 HHCHT013I Using HTTPROOT directory "F:\herc_html\"
16:11:14 HHCAO001I Hercules Automatic Operator thread started;
16:11:14 tid=00000990, pri=0, pid=2184
16:11:14 HHCHT006I Waiting for HTTP requests on port 80
16:11:16 HHCTE009I Client 127.0.0.1 connected to 3270 device 0:0700
16:11:25 ipl a80
John Johnston
2008-03-15 08:24:13 UTC
Permalink
1st off, the "problem", as reported, does not seem to
be a problem with Hercules. It seems OS/390 has IPL'd
successfully and is processing the various started
tasks.

2nd, I see no evidence in the doc provided that there
is a failure in the TCPIP stack. Had the stack
actually been started at the time of the error? The
message you are complaining about(GFSC099I) was issued
by the NFS client portion of OS/390. Also, the "I" on
the end means informational.

3rd, have you looked at ALL the messages that have
been issued? IBM msgs can be looked up here
http://www-03.ibm.com/systems/z/os/zos/bkserv/lookat/
.

Looking up GFSC099I at the above site says that that
it is a message intended to provide diagnosis
information to IBM Support.

I'd suggest that you go and chat to the sysprog(s) who
configured your MVS system and TCPIP tasks (The
GFSC729W msg suggests that some more work may also be
needed).

Whilst OS/390 2.10 has been out of support for some
time now, the documentation is still available online
here
http://www-03.ibm.com/systems/z/os/zos/bkserv/v2r10books.html
. you might want to retrieve it while you can.







Get the name you always wanted with the new y7mail email address.
www.yahoo7.com.au/y7mail
au1john
2008-03-15 08:31:21 UTC
Permalink
Redfaced here..

Please accept my sincere apologies Puck.
I was totally distracted by the title and logs, both of which are not
relevant to the FTP problem.
Post by puck64au
reverse, but I cannot connect from WinXP via FTP Port 21 or use port
23
for TSO Connections (HostExplorer v6)
So now the first question to ask is.. Has this worked before? and if
so, what has changed?



I apologise once again.
puck64au
2008-03-15 10:13:06 UTC
Permalink
Post by au1john
Redfaced here..
Please accept my sincere apologies Puck.
I was totally distracted by the title and logs, both of which are not
relevant to the FTP problem.
Post by puck64au
reverse, but I cannot connect from WinXP via FTP Port 21 or use port
23
for TSO Connections (HostExplorer v6)
So now the first question to ask is.. Has this worked before? and if
so, what has changed?
I apologise once again.
Hi John,
Thanks for the reply.
Yep all was working in December 2007 on 2 machines (both running XP 2
dif versions of Herc) now both don't work :(((((
I have moved dasd and herc from machine to machine restored ghosted
versions of XP (where everyting worked). STILL BUSTED:(
I have a feeling an ID has expired in RACF

Regards
Mark
au1john
2008-03-15 11:24:31 UTC
Permalink
Post by puck64au
Hi John,
Thanks for the reply.
Yep all was working in December 2007 on 2 machines (both running XP 2
dif versions of Herc) now both don't work :(((((
I have moved dasd and herc from machine to machine restored ghosted
versions of XP (where everyting worked). STILL BUSTED:(
I have a feeling an ID has expired in RACF
Mark,

If, as you suggest, it is an expired ID then, QED, it is not a
Hercules problem.

You need to analyse your SYSLOG in more detail I'd suggest. If you
can't see any ICH* messages there indicating such problems, then you
would need to look at the SMF records that should have been cut.


Good luck.
puck64au
2008-03-15 12:49:56 UTC
Permalink
Hi John,
The Expired ID is a guess, based on "badXid" ??? bad execution id ???.

I do not have the expertise to debug on a system level, I was a lowly
programmer ina former life :-)

No time like the present to learn :-)

Thanks for the Hint for ICH* in the syslog
and a look at the SMF records (if cut)

I found this from the syslog...
"1 J E S 2 J O B L O G -- S Y S T E M S
Y S 1 -- N O D E N 1
0
16.12.29 STC00002 ---- SATURDAY, 15 MAR 2008 ----
16.12.29 STC00002 ICH70006I USERID (VTAM ) ASSOCIATED WITH
PROCEDURE (*UNKNOWN) HAS
BEEN REVOKED FROM THE SYSTEM;
VERIFICATION FOR THE
PROCEDURE CONTINUES.
16.12.30 STC00002 IEF695I START VTAM WITH JOBNAME VTAM IS
ASSIGNED TO USER VTAM , GROUP SYS1
16.12.30 STC00002 $HASP373 VTAM STARTED
16.12.30 STC00002 IEF403I VTAM - STARTED - TIME=16.12.30
16.12.35 STC00002 ICH408I USER(VTAM ) GROUP(SYS1 ) NAME
(####################)
LOGON/JOB INITIATION - REVOKED USER ACCESS
ATTEMPT
16.12.35 STC00002 IST093I ISTCDRDY ACTIVE
"

Regards,
Mark
Post by au1john
Mark,
If, as you suggest, it is an expired ID then, QED, it is not a
Hercules problem.
You need to analyse your SYSLOG in more detail I'd suggest. If you
can't see any ICH* messages there indicating such problems, then you
would need to look at the SMF records that should have been cut.
Good luck.
Peter Vels
2008-03-15 20:50:49 UTC
Permalink
Try this (I haven't verified it, I'm not able to at the moment):

At the MVS console enter:

logon

Then enter the userid and password of a user with enough RACF authority to
resume the VTAM userid.

Then, assuming your RACF command prefix is "#', enter the following:

#alu vtam resume

logoff

re-IPL

Good luck.

Peter
Post by puck64au
Hi John,
...
I found this from the syslog...
... 16.12.29 STC00002 ICH70006I USERID (VTAM ) ASSOCIATED WITH
PROCEDURE (*UNKNOWN) HAS
BEEN REVOKED FROM THE SYSTEM;
VERIFICATION FOR THE
PROCEDURE CONTINUES.
16.12.30 STC00002 IEF695I START VTAM WITH JOBNAME VTAM IS
ASSIGNED TO USER VTAM , GROUP SYS1
16.12.30 STC00002 $HASP373 VTAM STARTED
16.12.30 STC00002 IEF403I VTAM - STARTED - TIME=16.12.30
16.12.35 STC00002 ICH408I USER(VTAM ) GROUP(SYS1 ) NAME
(####################)
LOGON/JOB INITIATION - REVOKED USER ACCESS
ATTEMPT
16.12.35 STC00002 IST093I ISTCDRDY ACTIVE
"
[Non-text portions of this message have been removed]
puck64au
2008-03-15 23:47:29 UTC
Permalink
Hi Pete,
thanks for the advise.
I tried it, but still busted:(

I still can't get past this (console capture)
- 16.14.13 STC00027 GFSA348I OS/390 NETWORK FILE SYSTEM SERVER
(HDZ11TS)
- STARTED.
- 16.14.16 STC00026 IMW3536I SA 16842763 0.0.0.0:80 * * READY
00- 16.14.52 STC00006 GFSC099I (D) CTMRD 11 TMRD :
00000003:TmrD
- pidTmr(00010012) badXid
- 16.14.52 STC00006 GFSC729W OS/390 NFS CLIENT IS UNABLE TO
RESERVE 384
- SOCKETS, CURRENT MAXFILEPROC IS 256
- 16.14.52 STC00006 GFSC700I OS/390 NETWORK FILE SYSTEM CLIENT
(HDZ11TC)
- STARTED

regards,
Mark
Post by Peter Vels
logon
Then enter the userid and password of a user with enough RACF
authority to
Post by Peter Vels
resume the VTAM userid.
#alu vtam resume
logoff
re-IPL
Good luck.
Peter
Post by puck64au
Hi John,
...
I found this from the syslog...
... 16.12.29 STC00002 ICH70006I USERID (VTAM ) ASSOCIATED WITH
PROCEDURE (*UNKNOWN) HAS
BEEN REVOKED FROM THE SYSTEM;
VERIFICATION FOR THE
PROCEDURE CONTINUES.
16.12.30 STC00002 IEF695I START VTAM WITH JOBNAME VTAM
IS
Post by Peter Vels
Post by puck64au
ASSIGNED TO USER VTAM , GROUP SYS1
16.12.30 STC00002 $HASP373 VTAM STARTED
16.12.30 STC00002 IEF403I VTAM - STARTED - TIME=16.12.30
16.12.35 STC00002 ICH408I USER(VTAM ) GROUP(SYS1 ) NAME
(####################)
LOGON/JOB INITIATION - REVOKED USER ACCESS
ATTEMPT
16.12.35 STC00002 IST093I ISTCDRDY ACTIVE
"
[Non-text portions of this message have been removed]
somitcw
2008-03-16 00:00:13 UTC
Permalink
Post by puck64au
Hi Pete,
thanks for the advise.
I tried it, but still busted:(
I still can't get past this (console capture)
Exactly what is it that you can't get past?
Post by puck64au
- 16.14.13 STC00027 GFSA348I OS/390 NETWORK
FILE SYSTEM SERVER (HDZ11TS) - STARTED.
Informational message.
Post by puck64au
- 16.14.16 STC00026 IMW3536I SA 16842763
0.0.0.0:80 * * READY
Informational message.
Post by puck64au
00- 16.14.52 STC00006 GFSC099I (D) CTMRD 11
TMRD : 00000003:TmrD
Informational message.
Post by puck64au
- pidTmr(00010012) badXid
- 16.14.52 STC00006 GFSC729W OS/390 NFS CLIENT
IS UNABLE TO RESERVE 384 - SOCKETS, CURRENT
MAXFILEPROC IS 256
Yahoo search finds:

GFSC729Wz/OS NFS CLIENT IS UNABLE TO RESERVE
d_digit SOCKETS, CURRENT MAXFILEPROC IS d_digit

Explanation:
The maximum number of socket descriptors that
a process can have open concurrently has been
exceeded. Increase the MAXFILEPROC parameter
value in the BPXPRMxx member to bypass this
problem. See z/OS UNIX System Services Planning
for more information about specifying the
MAXFILEPROC value.

System action:
The operation ended with an error. The NFS client
processing continues.

System programmer response:
Increase the MAXFILEPROC parameter value in the
BPXPRMxx member to bypass the problem.
Post by puck64au
- 16.14.52 STC00006 GFSC700I OS/390 NETWORK
FILE SYSTEM CLIENT (HDZ11TC) - STARTED
Informational message.
Post by puck64au
regards,
Mark
- - - snipped - - -
puck64au
2008-03-16 13:12:29 UTC
Permalink
Hi All,

Many thanks to all those who replied with assistance, or read my post.

I managed to resolve the problem. :)))

I remembered (hard to believe) that I had installed an update for my
Marvel Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller from
the Microsoft Update Site.

I Rolled back the driver and altered the settings to those that were
in effect prior to the update (lucky I kept some screen prints)

I then rebooted XP and IPL OS390, I now have FTP XP --> OS390 and TSO
via 192.168.0.4 port 23.

The mmotherboard has 2 Ethernet controllers, this one I can make
changes needed to get TCPIP working on OS390.

Regards
Mark
John Johnston
2008-03-16 13:39:21 UTC
Permalink
Hello Mark,

I'm glad you have resolved your problem.

However, the biggest problem we had in helping you was
that information you posted here as what you thought
were the symptoms of the problem was in no way related
to the problem you had. The logged messages you gave
us were in no way related to FTP. I also suspect those
logged messages you gave us are still happening.


Perhaps my "what has changed?" set you thinking and
you then went back to look at the host OS, then
reverting the driver and settings.
From your description of the resolution and some
knowledge of what the network adapters can do, I
suspect that TCP checksum offload may have been your
problem. You may be able to roll the driver forward,
and then disable the Checksum offload.


(I'm guessing you are in WA BTW)
Hi All,
Many thanks to all those who replied with
assistance, or read my post.
I managed to resolve the problem. :)))
I remembered (hard to believe) that I had installed
an update for my
Marvel Yukon 88E8001/8003/8010 PCI Gigabit Ethernet
Controller from
the Microsoft Update Site.
I Rolled back the driver and altered the settings to
those that were
in effect prior to the update (lucky I kept some
screen prints)
I then rebooted XP and IPL OS390, I now have FTP XP
--> OS390 and TSO
via 192.168.0.4 port 23.
The mmotherboard has 2 Ethernet controllers, this
one I can make
changes needed to get TCPIP working on OS390.
Regards
Mark
------------------------------------
http://groups.yahoo.com/group/hercules-390
http://www.hercules-390.orgYahoo! Groups Links
Get the name you always wanted with the new y7mail email address.
www.yahoo7.com.au/y7mail
puck64au
2008-03-17 09:38:35 UTC
Permalink
Hi John,

Missed by that much :) no NSW.

I was a Programmer in a previous life without any System programming
experience,so you can see why I posted TCPIP Error with the "badXid".

When I IPL I look for the following message from Herculese "HHCCT073I
0E20: TUN device tun0 opened". This signifies to me that I have TCPIP.

The console display stopped at ("STC00006 GFSC700I OS/390 NETWORK
FILE SYSTEM CLIENT (HDZ11TC)- STARTED") where if TCPIP was working
the console would continue issuing messages.

I was REALLY clutching at straws, I could connect via 127.0.0.1:3270
but not 192.168.0.4:23. I could ping into and out of OS390, I could
FTP connect to the host but not host to OS390. On Sunday night I had
an epiphany, I remembered that I had an update to the Ethernet driver
from Microsoft so I rolled it back and made the required updates that
get it up and running for herc. Rebooted and I was off and running.

Note that there is nothing in the properties for either network card
that says "Checksum offload" so it was trial and error to get it
going the first time;)

I have "Hardware Checksumming" on the Marvel card but the other (I
forget its name) had nothing like it, so I disabled it in the BIOS
and use the Marvel.

I need a book... "Hercules, OS390 and TCPIP on Windows FOR DUMMIES"

Regards,
Mark
Post by John Johnston
Hello Mark,
I'm glad you have resolved your problem.
However, the biggest problem we had in helping you was
that information you posted here as what you thought
were the symptoms of the problem was in no way related
to the problem you had. The logged messages you gave
us were in no way related to FTP. I also suspect those
logged messages you gave us are still happening.
Perhaps my "what has changed?" set you thinking and
you then went back to look at the host OS, then
reverting the driver and settings.
From your description of the resolution and some
knowledge of what the network adapters can do, I
suspect that TCP checksum offload may have been your
problem. You may be able to roll the driver forward,
and then disable the Checksum offload.
(I'm guessing you are in WA BTW)
Post by puck64au
Hi All,
Many thanks to all those who replied with
assistance, or read my post.
I managed to resolve the problem. :)))
I remembered (hard to believe) that I had installed
an update for my
Marvel Yukon 88E8001/8003/8010 PCI Gigabit Ethernet
Controller from
the Microsoft Update Site.
I Rolled back the driver and altered the settings to
those that were
in effect prior to the update (lucky I kept some
screen prints)
I then rebooted XP and IPL OS390, I now have FTP XP
--> OS390 and TSO
via 192.168.0.4 port 23.
The mmotherboard has 2 Ethernet controllers, this
one I can make
changes needed to get TCPIP working on OS390.
Regards
Mark
------------------------------------
http://groups.yahoo.com/group/hercules-390
http://www.hercules-390.orgYahoo! Groups Links
Get the name you always wanted with the new y7mail email
address.
Post by John Johnston
www.yahoo7.com.au/y7mail
au1john
2008-03-17 10:15:54 UTC
Permalink
Hi Mark,

Responses interspersed...
Post by puck64au
Hi John,
Missed by that much :) no NSW.
Only "that much" eh? totally different sides of the continent.. I
guessed WA because of the timing of your postings. For the Yanks, I'd
suggest that would be almost equivalent to FL vs CA.

I'm in NSW too (Sydney metro).
Post by puck64au
I need a book... "Hercules, OS390 and TCPIP on Windows FOR DUMMIES"
is the close
This,
http://www.softdevlabs.com/Hercules/ctci-w32-index.html
is the closest we have, but I suspect you have already seen that as
you have used the device addresses as outlined in the examples pointed
to from that page.
Post by puck64au
Regards,
Mark
John

puck64au
2008-03-15 12:21:24 UTC
Permalink
Post by au1john
Redfaced here..
Please accept my sincere apologies Puck.
I was totally distracted by the title and logs, both of which are not
relevant to the FTP problem.
Post by puck64au
reverse, but I cannot connect from WinXP via FTP Port 21 or use port
23
for TSO Connections (HostExplorer v6)
So now the first question to ask is.. Has this worked before? and if
so, what has changed?
I apologise once again.
Hi John,
Thanks for the reply.
Yep all was working in December 2007 on 2 machines (both running XP 2
dif versions of Herc) now both don't work :(((((
I have moved dasd and herc from machine to machine restored ghosted
versions of XP (where everyting worked). STILL BUSTED:(
I have a feeling an ID has expired in RACF

Regards
Mark
Loading...