Re: Testing a TELNET exit point

["Steve Landess" <sjl_123@xxxxxxxxxxx>]

Pete,

Try putting a DSPLY operation in the RPG program with a result field
specified.

Since the exit point program doesn't run interactively, the message will go
to the system operator's message queue for an answer.  At this point, you
can determine the job name, user name, and job number of the job where the
exit program is running.

Then use STRSRVJOB to service the job, and debug the exit program with
STRDBG.

This is basically what I did to debug the FTP exit point program that I
wrote.

Steve Landess
Austin, Texas
(512) 423-0935

> Pete wrote:
> After scrubbing the web for an example of an RPG OPM Telnet Exit point
> example with no luck, I finally was able to find an ILE RPG example that I
> understood well enough to modify and compile (a feat in itself).  Now that
I
> have it compiled, my challenge is to get it to work!
>
> I registered the program at the QIBM_QTG_DEVINIT format INIT0100 exit
point,
> stopped and restarted the Telnet service and nothing!  The exit program
is,
> at minimum, supposed to issue a message to the QSYSOPR message queue that
> the Telnet device was created for user XXXXXXXXXX but I don't get anything
> that indicates that the exit point is being hit.
>
> Perhaps this should go to programmers topic but I think the program is
> working correctly.  What I don't know is if this program is registered at
> correct point or under the correct conditions.  What I want to accomplish
> with the program is to verify that the user who starts the telnet session
is
> authorized to do so over an SSL connection.  The program logic looks
> correct, but I can't evaluate that if the program never gets triggered and
> that seems to be the current problem.
>
> Any pointers?  And, on the offhand chance that it is an ILE "ignorance"
> problem, the program was created with the crtbndrpg command using default
> creation values and registered using the ADDEXITPGM command with default
> values (except program name and library).  I can see that the program is
> registered using the WRKREGINF command.
>
> TIA,
>
> Pete Helgren