Re: V5R4M0 File QDPTDSP in library QSYS member or device *N not opened.

[Michael Ryan <michaelrtr@xxxxxxxxx>]

File sent as a save file to the OP.

On Thu, Jun 24, 2010 at 9:33 AM, <rob@xxxxxxxxx> wrote:

> Have a recent SAVSYS?
> http://tinyurl.com/QDPTDSP
> or
>
> http://www-01.ibm.com/support/docview.wss?rs=0&dc=DB520&dc=D900&dc=D800&dc=DA900&dc=DA800&q1=QDPTDSP+AND+AS400KBXXYYZZRCH&uid=nas177286821c7169070862565c2007d226b&loc=en_US&cs=UTF-8&lang=all
>
> I don't run anything as old as 5.4, heck 6.1 is being phased out.  But I
> do have a few sets of old release media.
>
> If some person on 5.4 who stays very current with ptf's could run
> DSPOBJD OBJ(QDPTDSP) OBJTYPE(*FILE) DETAIL(*SERVICE)
> and jot down if that has a ptf number assigned to it then you could order
> that ptf and that might restore the object.
>
> It sounds like they tried some strange migration like restore a v5r1
> system on to new hardware and reinstall V5R4.
>
> I wonder if CHKPRDOPT PRDID(*OPSYS) would pass or fail?  Or, if a
> GO LICPGM
> 10. Display installed licensed programs
> would show any with a status of Error or some such thing?
>
> Rob Berendt
> --
> Group Dekko Services, LLC
> Dept 01.073
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> From:   Guy Henza <guyhenza@xxxxxxxxxxx>
> To:     <midrange-l@xxxxxxxxxxxx>
> Date:   06/24/2010 08:54 AM
> Subject:        V5R4M0 File QDPTDSP in library QSYS member or device *N
> not opened.
> Sent by:        midrange-l-bounces@xxxxxxxxxxxx
>
>
>
>
> I just started at QS/Togo and tried to compile my first program and got
> the following when I hit F4;
>
>
>
> Message ID . . . . . . :   CPF4182       Severity . . . . . . . :   50
> Message type . . . . . :   Information
> Date sent  . . . . . . :   06/24/10      Time sent  . . . . . . : 08:42:35
>
>
> Message . . . . :   File QDPTDSP in library QSYS member or device *N not
>
>  opened.
> Cause . . . . . :   File was not opened because an error occurred.  If
> this is
>  a device file, the device may not be usable.
>
>
>
> The program will compile, I just can't prompt it.  It seems to happen on
> any F4 not just compile.  Can't prompt debug, call, wrkactjob or any other
> command.
>
>
>
> Anyone got a spare QDPTDSP they can loan me?  V5R4M0
>
>
>
> Regards,
>
> Guy Henza
> guyhenza@xxxxxxxxxxx
>
>
>
> _________________________________________________________________
> The New Busy is not the old busy. Search, chat and e-mail from your inbox.
>
> http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_3
>
> --
> 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.