trying to find the PTF that broke CLP38 pgms that use ALCOBJ. -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: trying to find the PTF that broke CLP38 pgms that use ALCOBJ.
From: Gerald Magnuson <gmagqcy.midrange@xxxxxxxxx>
Date: Tue, 31 Aug 2021 13:36:47 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

after putting several PTF groups for 7.4, we did an IPL this weekend.
we started to get CPD0162 messages on ALCOBJ and DLCOBJ commands within
CLP38 programs.
I googled and found a PTF, SI76484, that stated the problem was in the
parameter checking of the QSYS38 commands. However, applying that ptf
didn't seem to help, in that I just had to go ahead and convert those CLP38
programs that use ALCOBJ / DLCOBJ to CLP.

also, from reading the fixing PTF SI76484, I am not finding out what was
the PTF that broke this?

(why can't I figure out what PTF's are going to break things before I break
them?)

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: trying to find the PTF that broke CLP38 pgms that use ALCOBJ. , Jack Woehr

This mailing list archive is Copyright 1997-2026 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.