× 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.



This is a stupid question from me...

Is that a requirement? I thought they took affect when registered. I
didn't think an IPL was required.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rich
Loeber
Sent: Friday, June 27, 2025 3:19 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Exit point program for QIBM_QZSO_SIGNONSRV

Have you done an IPL since registering the point?

Rich Loeber
Kisco Systems
________________________________
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of
smith5646midrange@xxxxxxxxx <smith5646midrange@xxxxxxxxx>
Sent: Friday, June 27, 2025 3:01:54 PM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Exit point program for QIBM_QZSO_SIGNONSRV

I am trying to write an exit program for QIBM_QZSO_SIGNONSRV in RPGLE and
failing miserably. I looked using WRKREGINF and it was registered correctly
but the logic in it is not being executed. I have a dsply statement to a
specific MSGQ at the top of the program and the value DSPLYed is not showing
up. If I call the program manually and pass parms, it does do the DSPLY.



I've never written an exit program before so I really don't know what I am
doing. Does anyone have a program for this exit point that they would be
willing to share with me? I found an example on the IBM website but it says
the parms are V5.1 and prior and it is written in CL, not RPGLE. We are
running V7.3.



Thanks in advance.





--
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.

--
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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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