× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Chris,

When you IPL, are doing a manual IPL to restricted state.
Check the locks at that point.

Paul

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Christopher J. Wager | 56K Projects
Sent: Sunday, October 25, 2020 8:56 AM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: QSYS2/SYSIXADV - Damaged

________________________________
CAUTION: This email originated from outside of the PENCOR network. Do not click on any links or open attachments unless the sender is known, and the content is verified as safe.
________________________________

Afternoon All,

I cannot follow the steps to recover QSYS2/SYSIXADV because the file is in use and locked

As per this page.

https://www.ibm.com/support/pages/how-recover-damaged-sysixadv-file
How to Recover from a Damaged SYSIXADV File - IBM<https://www.ibm.com/support/pages/how-recover-damaged-sysixadv-file>
Resolving The Problem. The Index Advisor file used when the optimizer determines that a permanent index might be beneficial - and it returns the key columns necessary to create the suggested index into QSYS2/SYSIXADV.
www.ibm.com

The first set of instructions will not work as I get an error saying Cannot allocate object SYSIXADV

and I cannot DLTF the files as SYSIXADV is in use.

the output of WRKOBJLCK is as follows:

Work with Object Locks
System: DEEPBLUE
Object . . . . : SYSIXADV Type . . . . . : *FILE-PHY
Library . . : QSYS2 ASP device . . : *SYSBAS

Type options, press Enter.
4=End job 5=Work with job 8=Work with job locks

Opt Job User Lock Status Scope Thread
QDBSRV04 QSYS *SHRRD HELD *JOB
*SHRRD HELD *JOB

It's been sat like that now for a good 48 hours and QDBSRV04 is a System job so I can't use 4 to end it

I can't complete the steps to recover this unless I can release the lock and I cannot release the lock.

How do I sort this?

I have already tried these steps,

If the previous steps do not work due to locks, you can also try the following steps:

1. ADDENVVAR ENVVAR(QIBM_NO_INDEX_ADVICE) VALUE('') LEVEL(*SYS) 2. IPL 3. Repeat the DLTF steps if needed 4. RMVENVVAR ENVVAR(QIBM_NO_INDEX_ADVICE) LEVEL(*SYS) 5. IPL

But the result is the same I still cannot delete the file as its locked by QDBSRV04

Thanis
Chris










________________________________
From: Christopher J. Wager | 56K Projects
Sent: 25 October 2020 01:18
To: midrange-l@xxxxxxxxxxxxxxxxxx <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: QSYS2/SYSIXADV - Damaged

Evening All,

Okay so I resolved my initial issue with QSYS2/SYSROUTINE, did a SAV21 (KEEP THIS)

Then I installed a cumulative ptf, now I have a problem with QSYS2/SYSIXADV

Tried to follow the instructions here https://www.ibm.com/support/pages/how-recover-damaged-sysixadv-file
How to Recover from a Damaged SYSIXADV File - IBM<https://www.ibm.com/support/pages/how-recover-damaged-sysixadv-file>
Resolving The Problem. The Index Advisor file used when the optimizer determines that a permanent index might be beneficial - and it returns the key columns necessary to create the suggested index into QSYS2/SYSIXADV.
www.ibm.com

When I do step one I get "Cannot allocate object SYSIXADV"

I then tried the second set intructions for if locks caused a problem

But after doing step 1 and 2 the system still won't let me delete QSYS2/SYSIXADV claiming it is locked.

using WRKOBJLCK it appears to be locked by QDBSRV05 I have no idea what I am doing wrong.

Can someone tell me.

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

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.