Todd
You can stop reloading NCP. NCP appears logically to be involved with COS -
because there is reference to a COS table in the NCP source - only if you
have SNI. Even then it is a VTAM-only parameter.
This looks like a "'let go' without ensuring the same skill is available"
problem - or maybe "issue". Incidentally I try to help with *problems*
rather than *issues*[1] - although I sometimes try to help when the subject
under consideration truly is an "issue" rather than a "problem".
Perhaps you should post your COS table source so that we can verify that it
indeed contains an entry with the name BATCH.
If you post again, please indicate the key parts of the session
configuration so that we can be sure you are working with the correct VTAM.
You should browse the content of the ISTVTCOS module in order to be sure
that it really does contain the name BATCH which should be easily visible.
If you are running SNI - and if you still have NCPs, this is more likely
today than it used to be, SNI being one of the trickiest NCP functions to
replace - then your problem may not be ISTVTCOS but a COS table named in the
NCP source.
Without checking the manuals - which you probably have done - I would say
you are doing the right thing in ensuring that ISTVTCOS is being made
available to VTAM.
Chris Mason
[1] Having heard on the news (BBC) only today that a university lecturer had
become totally fed up with his even advanced students mangling the language
in their written work with the result that he has published his concerns for
the benefit the "Queen's English Society", I decided I would request the
assistance of this society in combating the misuse of the word "issue" I
find endemic in much written - here in this list particularly - and spoken -
even BBC TV drama programs - material these days. Watch this space!
----- Original Message -----
From: "Todd Burrell" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
To: <[email protected]>
Sent: Monday, August 13, 2007 5:14 PM
Subject: COS table missing
We are having an issue with our COS table and VTAM. We upgraded over the
weekend and missed copying in the ISTSDCOS module into SYS1.VTAMLIB.
Now that we are up, we are having an NDM transmit fail with the following
message:
IST1138I REQUIRED COS NAME BATCH UNDEFINED
I have tried reloading the NCP, and I also have tried to load the table
dynamically with the following command:
F NET,TABLE,OPTION=LOAD,NEWTAB=ISTSDCOS
This command appeared to work, and then we did another NCP reload.
None of this has corrected the NDM transmit. We get the same error
message. Does anyone know how to get VTAM to reload and recognize this
COS table without recycling VTAM? Or does anyone know of any other sort of
work around? This is a critical transmission, and I would rather not have
to
cycle VTAM in the middle of the day for this issue.
Also, we are now on z/OS 1.8.
Thanks
Todd
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
