RE: (no subject)

Hi Peter,

I don't recall having any problems w/ DSPOBJD command in V5R1; the problem
we ran into when upgrading was w/ the WRKOUTQ command.  Actually, the
problem was more on our end; we had an old CL program that had the following
commands:
        WRKOUTQ    OUTQ(*ALL) OUTPUT(*PRINT)
        CPYSPLF    FILE(QPRTSPLQ) TOFILE(OUTQ) SPLNBR(*LAST)
IBM expanded some of the output, hence, changing the positon of some of the
data on the spooled file; when we parsed the OUTQ file (in latter commands),
we did not come up w/ the same results...  They may have added and/or
expanded fields in the DSPOBJD command too; not sure...

DeeDee Virgei

-----Original Message-----
From: Tauch, Peter [mailto:peter.tauch@erwagner.com]
Sent: Friday, December 20, 2002 10:30 AM
To: 'bpcs-l@midrange.com'
Subject: (no subject)


Hello,

We are upgrading from V4R5 to V5R1 on December 27th. I have heard from the
grapvine that there is a problem when doing a DSPOBJD and writing to an
*OUTFILE. Has anybody had this problem with any BPCS Programs. We are on 6.1
mixed mode.

Thanks,

Peter Tauch

(414) 449-8256

_______________________________________________
This is the SSA's BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/bpcs-l
or email: BPCS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.