Interesting - thanks for the help.
Luke
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of
Chris Mason
Sent: Tuesday, October 06, 2009 11:42 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Dynamically change FLDTAB back to the internal table
Luke
> Does anyone know what I'm missing or how to switch back to the default?
Indeed I do - becasue, like you, I have also fallen foul of a documentation
error in the description of the FLDTAB start option in the Communications
Server SNA Resource Definition Reference manual.
What it should say is the following:
<quote>
FLDTAB
>>----------------------------------><
| |
---FLDTAB=---table_name---|
| |
-NONE---------
Specifies whether VTAM uses a message-flooding prevention table to suppress
duplicate messages and, if so, which table will be used.
FLDTAB=NONE
Indicates that VTAM will not suppress duplicate messages that are sent to the
operator console or system hardcopy log.
FLDTAB=table_name
Indicates that VTAM uses a user-specified message-flooding prevention table
to determine which duplicate messages are to be suppressed. table_name is
the 1-8 character name of the table stored in the VTAM definition library
(VTAMLST).
If an attempt to load the specified table fails, VTAM issues an error message
and uses the VTAM internal table.
If you specify neither a table name nor NONE, VTAM will use an IBM-supplied
table located in VTAMLIB which has the name ISTMSFLI. This is an internal
version of the message-flooding prevention table which has the name
ISTMSFLD which can be found in the distribution library (SAMPLIB).
Notes:
1. If you issue a DISPLAY ID=ISTNOP command and the IBM-supplied message-
flooding prevention table is in use, the name of the table will be shown as
ISTMSFLD.
2. If you wish to indicate the IBM-supplied message-flooding prevention table
is in use in the specified start options, you may specify FLDTAB=ISTMSFLD
but you should also ensure that the table is copied from the distribution
library
(SAMPLIB) to the IBM definition library (VTAMLST).
</quote>
I have been meaning to submit this correction to the VTAM folk - and I may
get around to it yet - particularly after your experience.
The following notes are intended to go along with this suggested corrected
text:
<quote>
Comments:
1. Just try specifying FLDTAB=ISTMSFLD and see what sort of a mess you get
into!!!
2. "If you specify ISTMSFLD as the table name, VTAM will use the IBM-
supplied table located in the VTAM definition library." is plain wrong since we
have already established that "the VTAM definition library" means VTAMLST
and ISTMSFLD cannot be found in VTAMLST without a manual copy.
3. What happens when the supposed default FLDTAB=ISTMSFLD is specified
by not actually specifying anything is that VTAM quietly uses a pre-digested
version of ISTMSFLD - called ISTMSFLI - located in VTAMLIB.
</quote>
So if you want to use the MODIFY TABLE command to revert to the supplied
table, you need to copy the ISTMSFLD member from SAMPLIB into your
VTAMLST.
I discovered this because I was advising a customer for whom I was doing
some consulting by supplying him with a set of start options which included
any possibly relevant to him. This included FLDTAB=ISTMSFLD,[1] supposedly
the default specification - as currently specified in the manual and as you
indicate with your DISPLAY VTAMOPTS output - and we got an error message
saying something like your IST116I message, basically "I'd love to load the
table you specified but I just can't seem to find it! - sorry" - wildly
anthropomorphising as I used to in order to try to keep my students amused!
Well, "red faces, of course". This highly paid - a matter of opinion! -
consultant has fallen down on the job - again!
Sufficiently stung, I looked into what had gone wromg and came up with the
improved text for the FLDTAB start option above. Reputation restored, ordure
redirected to the hopeless manual authors - phew!
Chris Mason
[1] And indeed, we did discuss how to use the message flooding table in order
to suppress repeated appearances of a message may have been difficult to
eliminate any other way. Thus it was handy to have the standard table copied
to a marginally more accessible library.
On Tue, 6 Oct 2009 09:41:20 -0500, Rabbe, Luke
<luke.ra...@countryfinancial.com> wrote:
>At VTAM startup I don't specify FLDTAB so the default ISTMSFLD is used.
>
>
>
>D NET,VTAMOPTS,FUNCTION=MESSAGES
>
>IST097I DISPLAY ACCEPTED
>
>IST1188I VTAM CSV1R9 STARTED AT 03:28:15 ON 09/20/09 800
>
>IST1349I COMPONENT ID IS 5695-11701-190
>
>.
>
>.
>
>IST1189I FLDTAB = ISTMSFLD FSIRFMSG = OLUSSCP
>
>.
>
>.
>
>IST314I END
>
>
>
>I dynamically changed the FLDTAB using:
>
>F
NET,TABLE,OPTION=ASSOCIATE,ID=ISTNOP,NEWTAB=XXXXXXXX,OLDTAB=*,T
YPE=FLDTAB
>
>Then I wanted to dynamically change back to the default ISTMSFLD so I
issued:
>
>F
NET,TABLE,OPTION=ASSOCIATE,ID=ISTNOP,NEWTAB=ISTMSFLD,OLDTAB=*,TY
PE=FLDTAB
>
>But the command fails and I get this message group:
>
>IST097I MODIFY ACCEPTED
>IST116I MEMBER ISTMSFLD NOT FOUND ON VTAM DEFINITION LIBRARY
>IST863I MODIFY TABLE COMMAND FAILED-ISTMSFLD NOT FOUND 586
>IST864I NEWTAB=ISTMSFLD, OLDTAB=*, OPT=ASSOCIATE, TYPE=FLDTAB
>IST935I ORIGIN=***NA***, NETID=***NA***, ID=ISTNOP
>
>I don't see ISTMSFLD in my VTAM load libraries and ISTMSFLD has never
been in my definition libraries. Does anyone know what I'm missing or how to
switch back to the default?
>
>This isn't a big deal - I just want to be able to do it if I need to.
>
>Thank you,
>Luke Rabbe
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
