I believe this warning isn't about the files being updated on disk - but about the fact that these sample files have changed from the last maintenance level and you should check them in case you have used them. There may be new options, features, variables, commands, etc etc that are in the sample files and you want to think about applying to any past samples you started with and are now using in production.
Scott Rohling On Fri, Oct 29, 2010 at 5:15 PM, George Henke/NYLIC < george_he...@newyorklife.com> wrote: > > I just did PUT2PROD Level 1 and was checking the results. > > Everything finished clean, but VMFVIEW showed some warnings, DTCPRD3013W > and DTCPRD3043W. > > I have included the message descriptions from TCPIP Messages and Codes > below. > > The 3013 is says there are no entries in 5VMTCP40 CATALOG. > > I did comment out the LOAD BFS in 5VMTCP40 CATALOG per IBM's > recommendation, by putting a hyphen in column 1, to resolve an error at > apply time when BFS is not operational.. > > The other lines after it did seem to get processed. > > According to $VMFP2P $MSGLOG, they were copied to TCPMAINT's 591 from > 5VMTCP40 491 as is. > > But the 3043 message says they were modified and to check the changes. > > When I look at the files on 5VMTCP40 491 and TCPMAINT 591 they do not have > an updated Date/Time stamp. > > Yet the system still thinks they have been updated. > > Did the modification to 5VMTCP40 CATALOG interfere with something? > > WN:DTCPRD3013W No entries are available for processing > WN:DTCPRD3021W TCP2PROD processing completed with RC = 4 > WN:DTCPRD3043W File PROFILE STCPIP I has been updated; Its content > WN: should be reviewed for changes that may affect your use of > WN: this file > WN:DTCPRD3043W File SCEXIT SAMPASM I has been updated; Its content > WN: should be reviewed for changes that may affect your use of > WN: this file > WN:DTCPRD3043W File LDAP-DS SCONFIG I has been updated; Its content > WN: should be reviewed for changes that may affect your use of > WN: this file > WN:DTCPRD3043W File MPROUTE SCONFIG I has been updated; Its content > WN: should be reviewed for changes that may affect your use of > WN: this file > WN:DTCPRD3043W File SMTPCMDX SAMPEXEC I has been updated; Its content > WN: should be reviewed for changes that may affect your use of > WN: this file > WN:DTCPRD3043W File SMTPCMDX SAMPASM I has been updated; Its content > WN: should be reviewed for changes that may affect your use of > WN: this file > WN:DTCPRD3021W TCP2PROD processing completed with RC = 4 > > > *20.9.8 DTCPRD3013W* > > > ------------------------------ > > > *DTCPRD3013W* *No* *entries* *are* *available* *for* *processing* > > > *Explanation:* The designated TCP/IP product catalog file does not > contain any entries that identify files to be processed by the TCP2PROD > command, or the designated section contains no such entries. > > *System* *Action:* Command processing stops. > > *System* *Programmer* *Response:* Verify that the correct CATALOG file > name and section name have been specified as part of the command. If > correct, review the content of the relevant catalog file and section, and > ensure that the entries present exist in proper form; that is, the entries > are neither all commentary data nor all marked with the entry-bypass > operator (a hyphen). Also, verify that a corresponding end tag is present > for the designated catalog section. Correct any problems, then try the > command again. > > > > > > > > *DTCPRD3043W* *This* *message* *is* *formatted* *as* *follows:* > > > *Messages:* > > - *DTCPRD3043W* *File* *file_ID* *has* *been* *updated;* *its* *content > * *should* *be* > - *DTCPRD3043W* *reviewed* *for* *changes* *that* *may* *affect* *your* > *use* *of* *this* *file* > > *Explanation:* The content of the indicated sample file has been updated > by service that has been installed on the system. The changes to this file > are associated with functional changes to one or more TCP/IP program > components that have likewise been affected by service. > > *System* *Action:* Command processing continues. > > *System* *Programmer* *Response:* Upon completion of the command, review > the content of the indicated file and determine whether the changes that > have been introduced affect your use of any customized, production-use > counterpart to this file. For more information, consult the descriptions of > these changes described in the relevant APAR or other service documentation. > > > In some instances, it might help to compare the updated file with its > base-level counterpart (maintained on the TCPMAINT 2B2 Base Code minidisk), > so you can identify specific changes that might not be apparent in a > customized, production-use file. > > > *Michael Donovan <dono...@us.ibm.com>* > Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> > > 10/27/2010 04:30 PM > Please respond to > > The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> > > To > IBMVM@LISTSERV.UARK.EDU > cc > Subject > Re: Maintenance Warnings > > > > > George, > > Yes. PUT2PROD will rebuild the NSS/DCSS which were hit by service. > > Thanks! > Mike > > > > George Henke---10/27/2010 03:58:36 PM---Here is my NSS and DCSS so far, > after Service but before PUT2PROD. It shows GCS has been hit. > > From: > George Henke/NYLIC <george_he...@newyorklife.com> > To: > IBMVM@LISTSERV.UARK.EDU > Date: > 10/27/2010 03:58 PM > Subject: > Re: Maintenance Warnings > Sent by: > The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> > ------------------------------ > > > > > Here is my NSS and DCSS so far, after Service but before PUT2PROD. > > It shows GCS has been hit. > > When I put this same maintenance on in Level 2 and PUT2PROD, it showed > about 4 other NSS/DCSSes were also hit. > > Yet the system IPLed ok. > > Now I am applying the same maintenance at Level 1. > > Will not PUT2PROD rebuild these for me? > > Does the date/time stamp indicate it has been rebuilt or just updated? > > There is nothing in Automated Guide for Installation and Service that > speaks to building DCSS or NSS after Service or PUT2PROD. > > Is not the rebuild of NSS/DCSS done as part of either Service or PUT2PROD? > > pipe cp q nss iso | sort w6.2 d | cons * > *NSS 0057 NSS R 0124 2010-10-26 18:38:02 GCS NSS BLDNUC * > *NSS 0056 NSS A 1302 2010-06-23 15:18:06 CMS NSS MAINTSYS > *NSS 0054 NSS A 0045 2009-04-08 13:23:11 CMSBAM DCSS MAINT > *NSS 0053 NSS A 0015 2009-04-08 13:23:11 CMSDOS DCSS MAINT > *NSS 0052 NSS A 0258 2009-03-26 13:12:27 VTAM42 DCSS MAINT > *NSS 0041 NSS A 0142 2009-02-25 21:01:06 CMSAMS DCSS MAINT > *NSS 0040 NSS A 0255 2009-02-25 20:53:57 CMSVSAM DCSS MAINT > *NSS 0038 NSS A 0258 2009-02-25 20:08:42 HELPSEG DCSS BLDSEG > *NSS 0033 NSS A 0001 2009-02-25 19:24:49 DOSBAM DCSS MAINT > *NSS 0032 NSS A 0258 2009-02-25 19:05:02 NETVSG23 DCSS MAINT > *NSS 0030 NSS P 0124 2009-02-25 15:37:41 GCS NSS MAINT > *NSS 0028 NSS A 2050 2009-02-24 19:28:08 SCEEX DCSS BLDSEG > *NSS 0027 NSS A 0258 2009-02-24 19:27:54 CMSVMLIB DCSS BLDSEG > *NSS 0024 NSS A 1303 2008-07-03 08:15:11 ZCMS NSS MAINT > *NSS 0022 NSS A 0258 2008-07-03 08:12:16 NLSGER DCSS MAINT > *NSS 0021 NSS A 0258 2008-07-03 08:12:16 NLSKANJI DCSS MAINT > *NSS 0020 NSS A 0258 2008-07-03 08:12:16 NLSUCENG DCSS MAINT > *NSS 0019 NSS A 0258 2008-07-03 08:12:16 NLSAMENG DCSS MAINT > *NSS 0018 NSS A 0001 2008-07-01 12:46:57 PERFOUT DCSS MAINT > *NSS 0017 NSS A 0258 2008-07-01 12:45:00 SCEE DCSS MAINT > *NSS 0011 NSS R 0001 2008-07-01 12:34:05 MONDCSS DCSS MAINT > > > > > > >
