Re: QS36F file format error after migrating LPAR

[Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>]

Rob, I think you're right on.

I'm coming to the conclusion that I have two choices:

   1. Step back and make a type 21 restore booting directly from the tape
   work rather than try to install the opsys from virt opt and restore the
   libraries.
   2. Change my name, get plastic surgery, and become a missionary to
   Borneo.


On Mon, Apr 9, 2018 at 5:21 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

> Ok, seeing a file in QS36F, and seeing a format error, automatically makes
> me think the file became unlinked from it's IDDU definitition.  Possibly
> because the library containing the IDDU definitions was not restored, or
> in the wrong order, or some such thing.
> Kind of a WAG answer but gives you something to work on.
>
>
> 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:   Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
> To:     Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> Date:   04/06/2018 05:17 PM
> Subject:        QS36F file format error after migrating LPAR
> Sent by:        "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
>
>
>
> Almost there restoring/migrating to a new LPAR. What an odyssey! Thank
> everyone who has helped.
>
> Now making everything work.
>
> Have S36 applications throwing errors, e.g.:
>
> // QRYRUN INTRST01,INS.QRY,INTRST,DISPLAY,,,,,,,,,RECSEL,DETAIL
>  QRYRUN procedure is running
> Format INTRST01 not found in file INTRST in QS36F.
>
> The file INTRST is there. What magic button have I forgotten to push in
> restoring that this file has lost its connection with its format?
>
> --
> Absolute Performance, Inc.
> 12303 Airport Way, Suite 100
> Broomfield, CO 80021
>
> NON-DISCLOSURE NOTICE:  This communication including any and all
> attachments is for the intended recipient(s) only and may contain
> confidential and privileged information.  If you are not the intended
> recipient of this communication, any disclosure, copying further
> distribution or use of this communication is prohibited.  If you received
> this communication in error, please contact the sender and delete/destroy
> all copies of this communication immediately.
> --
> 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
>
>
> --
> 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