Three more V7R1 OS upgrade issues.
1) CPYFRMSTMF resulting in incorrect output, probably due to CCSID of 65535 on to file.
2) SSH file transfers failing because V7R1 created new directory openssh-4.7p1
Upgrade deleted both previous directories - openssh-3.5p1 and openssh-3.8.1p1
Current jobs were looking for either 3.5 or 3.8.
3) TTATOOLS version needs to match OS level, TTATOOLS needs to be upgraded.
-----Original Message-----
From: Steinmetz, Paul
Sent: Monday, November 25, 2013 4:07 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Upgrading R&D LPAR from V6R1 to V7R1 TR7
I installed from a V7R1 combined OS and PTF DSLO image, PTF were included as part of the image, except for latest CUM and TR7, which I had to download.
Initialize System (INZSYS) started automatically. I did not call this, but It didn't start until after I did an IPL. Time sent . . . . . . : 01:05:12
The previous errors occurred during the upgrade 00:38.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, November 25, 2013 2:45 PM
To: Midrange Systems Technical Discussion
Subject: RE: Upgrading R&D LPAR from V6R1 to V7R1 TR7
"Old format" makes me wonder. Did you run INZSYS?
http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/topic/rzahc/completeupgradechecklist.htm
step 4
Install the most current cumulative PTF package. (This package should have been ordered a week or two before your installation.) Use the instructions in the PTF Shipping Information Letter. Then return here and continue with the next step.
Note: If you do not install the cumulative PTF package now, you need to perform an IPL and let the Initialize System (INZSYS) process complete.
Before you do, set the IPL type to B (or the IPL type you use for everyday
operation) and then set the mode selection to Normal. Initialize System
(INZSYS) recovery has more information on INZSYS.
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: 11/25/2013 02:38 PM
Subject: RE: Upgrading R&D LPAR from V6R1 to V7R1 TR7
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Chuck,
Here are the specific error details.
This error occurred on two different LPARS, I expect it to occur again on my production LPAR.
5770SS1 V7R1M0 100423 Job Log PENCOR06
11/23/13 01:05:03 Page 5
Job name . . . . . . . . . . : DSP01 User . . . . . . :
PAULS Number . . . . . . . . . . . : 605841
Job description . . . . . . : QSYSJOBD Library . . . . . :
QSYS
MSGID TYPE SEV DATE TIME FROM
PGM LIBRARY INST TO PGM LIBRARY INST
From module . . . . . . . . :
QSQPROC
From procedure . . . . . . :
OPEN_SYSROUTINE
Statement . . . . . . . . . : 49624
To module . . . . . . . . . :
QSQPROC
To procedure . . . . . . . :
DROP_ROUTINE
Statement . . . . . . . . . : 23943
Message . . . . : SQL CATALOG
QSYS2/SYSROUTINE HAS AN OLD FORMAT. AN IPL
MAY BE NEEDED.
Cause . . . . . : This message is
used by application programs as a general
escape message.
SQL0901 Diagnostic 50 11/23/13 00:38:20.529271 QSQPROC
QSYS *STMT QSQPROC QSYS *STMT
From module . . . . . . . . :
QSQPROC
From procedure . . . . . . :
CLEANUP
Statement . . . . . . . . . : 51749
To module . . . . . . . . . :
QSQPROC
5770SS1 V7R1M0 100423
Job Log PENCOR06 11/23/13 01:05:03
Page 5
Job name . . . . . . . . . . : DSP01 User . . . . . . :
PAULS Number . . . . . . . . . . . : 605841
Job description . . . . . . : QSYSJOBD Library . . . . . :
QSYS
MSGID TYPE SEV DATE TIME FROM
PGM LIBRARY INST TO PGM LIBRARY INST
From module . . . . . . . . :
QSQPROC
From procedure . . . . . . :
OPEN_SYSROUTINE
Statement . . . . . . . . . : 49624
To module . . . . . . . . . :
QSQPROC
To procedure . . . . . . . :
DROP_ROUTINE
Statement . . . . . . . . . : 23943
Message . . . . : SQL CATALOG
QSYS2/SYSROUTINE HAS AN OLD FORMAT. AN IPL
MAY BE NEEDED.
Cause . . . . . : This message is
used by application programs as a general
escape message.
SQL0901 Diagnostic 50 11/23/13 00:38:20.529271 QSQPROC
QSYS *STMT QSQPROC QSYS *STMT
From module . . . . . . . . :
QSQPROC
From procedure . . . . . . :
CLEANUP
Statement . . . . . . . . . : 51749
To module . . . . . . . . . :
QSQPROC
To module . . . . . . . . . :
QSQPROC
To procedure . . . . . . . :
DROP_ROUTINE
Statement . . . . . . . . . : 23943
Message . . . . : SQL CATALOG
QSYS2/SYSROUTINE HAS AN OLD FORMAT. AN IPL
MAY BE NEEDED.
Cause . . . . . : This message is
used by application programs as a general
escape message.
SQL0901 Diagnostic 50 11/23/13 00:38:20.529902 QSQPROC
QSYS *STMT QSQPROC QSYS *STMT
From module . . . . . . . . : QSQPROC
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 51749
To module . . . . . . . . . : QSQPROC
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 51749
Message . . . . : SQL system error.
Cause . . . . . : An SQL system
error has occurred. The current SQL
statement cannot be completed successfully. The error will not prevent
other SQL statements from being processed. Previous messages may indicate
5770SS1 V7R1M0 100423 Job Log PENCOR06
11/23/13 01:05:03 Page 6
Job name . . . . . . . . . . : DSP01 User . . . . . . :
PAULS Number . . . . . . . . . . . : 605841
Job description . . . . . . : QSYSJOBD Library . . . . . :
QSYS
MSGID TYPE SEV DATE TIME FROM
PGM LIBRARY INST TO PGM LIBRARY INST
that there is a problem with the SQL statement and SQL did not correctly
diagnose the error. The previous message identifier was CPF9898. Internal
error type 7112 has occurred. If precompiling, processing will not continue
beyond this statement. Recovery .
. . : See the previous messages to
determine if there is a problem with the SQL statement. To view the
messages, use the DSPJOBLOG command if running interactively, or the WRKJOB
command to view the output of a precompile. An application program
receiving this return code may attempt further SQL statements. Correct any
errors and try the request again.
CPF87F8 Escape 40 11/23/13 00:38:20.529920
QZXMMRMX QDBXM *STMT QLPRPCPR QSYS 2158
From module . . . . . . . . :
DXXMRMX
From procedure . . . . . . :
SendMsg
Statement . . . . . . . . . : 3
Message . . . . : Unexpected
internal system error occurred in program
QZXMMRMX.
Cause . . . . . : An unexpected
error occurred in program QZXMMRMX. The
More...
internal error data is 1001 .
Recovery . . . : Look at the job log for
messages that indicate the reason for the error.
CPF8356 Diagnostic 30 11/23/13 00:38:20.556594 QTNEND
QSYS 1C66 QTNENDAG QSYS 0190
Message . . . . : Commitment
control ended with 0 local changes not
committed.
Cause . . . . . : Pending changes
were rolled back because there were
changes not committed at the time commitment control was ended for
commitment definition 31 with a logical unit of work id APPN.PENCOR06.X'ECC1DC0C3E91'.00001. There were 1 journals with a total of 0
record level changes. There were 0 object level changes. There were 0 API
commitment resources in the
commitment definition. Recovery . . . : No
recovery is required. Use the COMMIT or ROLLBACK command before ending
commitment control to avoid this situation. API commitment resources must be
removed using the Remove Commitment Resource API (QTNRMVCR). Technical
description . . . . . . . . : The
commitment definition identifier is
X'1001010000000005A6C7'. The activation group number is X'0000001F'. The
lock space id is UDB_010000000005A6C7. The lock space associated space id is
1. The XID is
X'00000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000'.
CPF3D95 Diagnostic 40 11/23/13 00:38:20.569635
QLPRPCPR QSYS 30E4 QLPRPCPR QSYS 30E4
Message . . . . : Exit program
processing failed.
Recovery . . . : See the
previously listed messages to determine the cause,
and then try the request again.
CPD3DC3 Diagnostic 30 11/23/13 00:38:20.572733
QLPRPCPR QSYS 30E4 QLPRPCPR QSYS 30E4
Message . . . . : Product 5770DE1
option 2 release V7R1M0 processing not
complete.
Cause . . . . . : Product 5770DE1
option 2 release V7R1M0 could not be fully
saved or restored because processing to complete saving or restoring library
QDBXM did not complete. Recovery .
. . : See the previously listed
messages to determine the cause, and then try the request again.
CPD3DFD Diagnostic 30 11/23/13 00:38:20.572740
QLPRPCPR QSYS 30E4 QLPRPCPR QSYS 30E4
Message . . . . : *PGM objects for
product 5770DE1 option 2 release V7R1M0
not restored.
5770SS1 V7R1M0 100423 Job Log PENCOR06
11/23/13 01:05:03 Page 7
Job name . . . . . . . . . . : DSP01 User . . . . . . :
PAULS Number . . . . . . . . . . . : 605841
-----Original Message-----
From: Steinmetz, Paul
Sent: Sunday, November 24, 2013 10:47 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Upgrading R&D LPAR from V6R1 to V7R1 TR7
Chuck,
Here's the error details.
ERROR PROCESSING VIEW USER_STG IN LIBRARY QSYS2.
ERROR PROCESSING VIEW USER_STG IN LIBRARY QSYS2.
ERROR PROCESSING VIEW USER_STG IN LIBRARY SYSIBMADM.
ERROR PROCESSING VIEW USER_STG IN LIBRARY SYSIBMADM.
ERROR PROCESSING VIEW VIEWS IN LIBRARY QSYS2.
Cross-reference notification 500 for request 0, type 2.
Job 605802/QSYS/QWCBTCLNUP ended on 11/23/13 at 00:09:30; 1.593 seconds used;
ERROR PROCESSING VIEW USER_STG IN LIBRARY QSYS2.
ERROR PROCESSING VIEW USER_STG IN LIBRARY SYSIBMADM.
*PGM objects for product 5770SS1 option 2 release V7R1M0 restored.
18 objects restored. 18 objects not restored.
26 objects restored. 10 objects not restored.
28 objects restored. 8 objects not restored.
Objects for product 5770DE1 option 2 release V7R1M0 not restored.
Job 605812/QLPINSTALL/QBCHINST ended on 11/23/13 at 00:24:20; 4.323 seconds u
3 objects restored from QTEMP to QTEMP.
5770DE1 option 02 not installed in job 605812/QLPINSTALL/QBCHINST.
*LNG objects for licensed program 5770DE1 option 02 not installed.
CPF3D80 Diagnostic 20 11/23/13 00:24:20.660712 QLPINATO
QSYS 1667 QLPINATO QSYS 1667
Message . . . . : 5770DE1 option 02
not installed in job
605812/QLPINSTALL/QBCHINST.
Cause . . . . . : Errors occurred
while installing *PGM objects for licensed
program 5770DE1 option 02 at
11/23/13 00:24:20. Recovery . . . : See
joblog 605812/QLPINSTALL/QBCHINST for more information. Use the Display Job
(DSPJOB) command to display the joblog. Correct any errors and then try the
request again.
CPF3D85 Diagnostic 30 11/23/13 00:24:20.682416 QLPINATO
QSYS 1667 QLPINATO QSYS 1667
Message . . . . : *LNG objects for
licensed program 5770DE1 option 02 not
installed.
Cause . . . . . : The *PGM objects
for licensed program 5770DE1 option 02
are in error, not installed, or not at the correct release level. The *PGM
objects for the licensed program must be successfully installed before the
*LNG objects can be installed.
Recovery . . . : See previous messages in
the joblog to determine if the *PGM objects for licensed program 5770DE1
option 02 failed to install.
Correct any errors, or install the required
licensed program. Then try the request again.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Sunday, November 24, 2013 1:57 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Upgrading R&D LPAR from V6R1 to V7R1 TR7
On 23-Nov-2013 12:15 -0800, Steinmetz, Paul wrote:
V7R1 OS Upgrade from DSLO image using automatic install complete.
2 minor issues.
1) 5770DE1 2 DB2 XML Extender
resulted in error status. This also occurred on another partition
months back. I expect the same error on upcoming Production V7R1
upgrade.
Anyone else run into this
I am curious... Any clarification on what the details behind "this"
might be? Effectively, _the error_ versus _an error_ for which the install failed, and thus left the option in an error status. That is, what specifically were the errors that preceded the 'not installed'
error issued for that RSTLICPGM 5770DE1 OPTION(02) [as performed by the user QLPINSTALL], as recorded in the LPP-install joblog?
Below is the fix.
1) IPL then signon as QSECOFR
2) DSPFFD QSYS/QADBXREF
- what do you see for the CCSID of the string columns?
3) CHGJOB CCSID() from step 2, the DSPFFD
4) CALL QSYS2/QSQXRLF (DLT QSYS2)
5) CALL QSYS2/QSQXRLF (CRT QSYS2)
6) CALL QSYS/QSQSYSIBM
7) CALL QSYS/QSQIBMCHK
Then run RSTLICPGM 5770DE1 OPTION(2).
Interesting. That seems to imply a dependence of that LPP option-2, on some object(s) that should exist as part of a properly-installed OS
OPTION(01) "Extended Base" feature which is a pre-requisite to install of any LPP. Makes one wonder if\what errors transpired in that other install joblog, for which that prior LPP install had failed, but for which apparently no similar notification of its failure was given.? But I recall that, unfortunately, the joblog of that OS option(01) [kwd XTND] install would have been /cleared/ if the install had been deemed to have been successful [a general /feature/ of auto-install]. As such, any problem would have to be inferred instead, from the side effects on any dependent features, or perhaps from what the output of a CHKPRDOPT *OPSYS
OPTION(01) DETAIL(*FULL) might have revealed, issued before the corrective\recovery actions were taken. Although as I recall [from when I was recruited to remake that installation], I never updated the Check Product Option for that option to fully diagnose any missing database file objects that were created-into versus being shipped-as part of the option.
Instead as I recall, some implicit corrective action, the step
(5) of the above, would be performed [¿if a SQL catalog VIEW file was missing?] so from the messages logged for that work, what objects were missing might be inferred; and that I deferred improvement of the notification of [any other] missing objects to the owners of the code.
2) PTF 5770HAS - SI50474 damaged status when attempting to apply.
Below is the fix:
- Delete SI50474
- Re-Order SI50474
- Load individually
- Apply individually
Hmm. That does not make much sense, unless the copy of that PTF was obtained as /test/ vs being a final\GA copy. The standard recovery for a PTF with a logically /damaged/ state, is to issue the LODPTF [irrespective its current status] and then APYPTF for that just-loaded PTF. Notably...
the PTF should *not* need to be deleted [no DLTPTF] nor re-ordered [no SNDPTFORD or equivalent]. Note that doing these operations separately\individually from other PTF activity, AFaIK, should not be necessary; beneficial, only to more closely reveal the progress of processing just that one PTF, versus the clutter that would be seen when loading and applying others at the same time.
The errors that were logged during the pre-damage apply [or remove] processing would identify the origin for the status=damaged; i.e.
reveals the condition for which the process since refers to the PTF as /damaged/ due to the prior inability to transition the PTF to the next logical\requested status. Preventing the error(s) should prevent the PTF being marked as /logically/ damaged when loaded and re-applied.
--
Regards, Chuck
--
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:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
--
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:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
--
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:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
