RE: V7R1 to V7R3 upgrade issues/resolutions -- MIDRANGE-L

Adding 2 more issues to this thread/list.

5) I don't start IP6, only IP4 in QSTRUP.

STRTCP STRSVR(*YES) STRIFC(*YES) STRPTPPRF(*YES) STRIP6(*NO) /* CHGIPLA STRTCP *NO ; NEED TO STRTCP IN QSTRUP TO DISABLE IPV6 */

Since upgrading to V7R3, I'm seeing this error in my nightly save.
TCP8A4E Diagnostic 30 03/04/18 22:04:42.130560 QTOCXMLCHK QSYS *STMT QTOIRTVI QSYS *STMT
From user . . . . . . . . . : QSYS
From module . . . . . . . . : QTOCXMLCHK
From procedure . . . . . . : zSendMessage__FPcN21lN21
Statement . . . . . . . . . : 18
To module . . . . . . . . . : QTOIRTVI
To procedure . . . . . . . : main
Statement . . . . . . . . . : 146
Message . . . . : File error with reason code 0001 for file
/QIBM/USERDATA/OS400/TCPIP/IP6/QTOCTCPIP6CONFIGLIR.XML.
Cause . . . . . : An error occurred while verifying file
/QIBM/USERDATA/OS400/TCPIP/IP6/QTOCTCPIP6CONFIGLIR.XML. The reason code is
0001. Reason codes and their meanings follow: 0001 - The file version is
not correct for the version of the operating system. 0002 - The file is
empty or does not exist. 0003 - The file parser detected an error with the
file. 0004 - An unexpected error occurred. Recovery . . . : For reason
code 0001, restore a correct version of the file onto the system. Then try
the request again. For reason code 0002, if the file name begins with
"/QIBM/USERDATA" recovery is not necessary. The file will be created as
needed by TCP/IP. For all other files, restore a correct version of the
file onto the system. Then try the request again. For reason code 0003,
check the previous messages in the job log. Correct any errors, then try
the request again. For reason code 0004, contact your service
representative.

Resolution:
IBM stated I need to start IPV6 at least once, that will clear this issue.

6) BRMS save time have increased 10-15 minutes, still researching, maybe SPECTRE/MELTDOWN PTFs and/or firmware.
Maybe some new object locks at V7R3, each lock will add 2 minutes, SAVWA wait time is set at 120, still researching.
BRMS behavior changes.
Differences in BRMS timestamps.
At V7R1 - BRMS timestamps all libraries with the timestamp of the last library saved.
At V7R3 - BRMS timestamps the library with the actual time saved.

Resolution - TBD

Paul

-----Original Message-----
From: Steinmetz, Paul
Sent: Wednesday, March 07, 2018 11:26 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: V7R1 to V7R3 upgrade issues/resolutions

I'm still confused on a few items related to 5770-SS1 (Option 29)

1)
< There are no plans to support IBM i 7.3.
Why was a V7R3 version included?

2) Are there code or objects included in option 29 that are used by NWS.
Because the NWS were varied on, (accidently) option 29 failed to install.
When I varied off the NWS, option 29 installed with no issue.

My R&D LPAR didn't have any NWS, option 29 installed without issue.

3) < This is not needed for guested lpars.
What about hosted lpars?

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Tuesday, March 06, 2018 8:49 AM
To: Midrange Systems Technical Discussion
Subject: Re: V7R1 to V7R3 upgrade issues/resolutions

<snip>
5770-SS1 (Option 29) Integrated Server Support The IBM i Integrated Server solution will only be supported with the hardware and operating system versions that are currently listed in the iSCSI Solution Guide.
There are no new planned enhancements to the IBM i Integrated Server product.
There are no plans to support any new System x hardware.
There are no plans to support any non-IBM hardware.
There are no plans to support IBM i 7.3.
</snip>

This is not needed for guested lpars.

http://www-01.ibm.com/support/docview.wss?uid=nas8N1022036

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 03/05/2018 04:42 PM
Subject: V7R1 to V7R3 upgrade issues/resolutions
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>

1) RPC not working on V7R3
Resolution:
IBM created PTF MF64720 to resolve the issue.

2) 5770SS1 29 Integrated Server Support failed to install.

I had 5 NWS, which I varied off prior to the PWRDWNSYS DELAY(60)
RESTART(*YES) IPLSRC(*IMGCLG) IMGCLG(V7R3OSPTF).
These varied on automatically, causing option 29 install to fail.
What I forgot to do is set these to *NO on IPL
Online at IPL . . . . . . . . . . : *YES (should have been set to *NO
just for the upgrade)
Resolution:
Varied them off.
RSTLICPGM LICPGM(5770SS1) DEV(OPTVRT01) OPTION(29)

3) VIP DocManager not working.

OS upgrade changed public authority from *USE to *EXCLUDE for system object QPMLPMGT. This object is used to confirm license product information.

Resolution:

Changed public authority to *USE for system object QPMLPMGT.

4) Spoolfiles being emailed were being rotated.

This should have been included as part of customization but was overlooked.

Resolution:

CHGPRTF *all/all q libraries Degree of page rotation . . . . *AUTO

V7R3 Default was *DEVD.

Other than the above,

Smooth upgrade using combined V7R3OSPTF DSLO image, single image called I_BASE_01.

All license keys and customization was included as part of the image.

Total time - 4 hours.

Save prior - 1 hour.

Upgrade - 45 minutes.

Upgrade check, resolution fixes, few remaining PTFs, IPL, - 1hour.

Save after - 1 hour.

Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx<mailto:psteinmetz@xxxxxxxxxx>
http://www.pencor.com/

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD