Re: WRKNETF API?

Jim

When I attempted to this I found I had to resort to a break handling 
program partly as I recall due to the lack of API's.

I simply provided two functions. One function on the sending system 
transmitted the file to a particular user and the second monitored the 
target users message queue. When a file was received it invoked the break 
handling program which parsed the message to get the net file details. Once 
I had those I was able to process the save file however I liked.

Due to the lack of details associated with a NETF I used the file name to 
provide some extra information for processing.

One idea I toyed with was having the send function load up a remote data 
queue with the details so that the receiving system could use these details 
to control processing. This would have involved trapping some of the 
sending message details and transmitting them with the other details to 
perform a smarter restore. I never got round to this chiefly because 
at  the time (V3R7 I think) a remote data queue would return a does not 
exist message rather than a communication broken message so it became a 
little messy.  I never really had the time to complete it all anyway and 
was struggling to convince the programmers to use the system anyway. It was 
an effort to create change control from anarchy so it was a slog all the way.

You could of course use a data queue to control a loop in CL and have a 
second CL that processed the file but I guess you are trying to have just 
one program handle it all.

If this doesn't get you started or provide food for thought feel free to 
request more details - I may even have the source somewhere to get you started.

Cheers
Evan Harris

>I've used the *outfile for WRKNETF before in CL programs to receive
>files, but I was hoping to be able to do it on a lower level.  I
>originally wanted this written in CL, and CL has the problem that it
>can only read one file once.  I want this in an endless loop scenario
>which means I'm going to have to have one CL program call another CL
>program to do the reading and checking, which I don't really like for
>maintenance and design issues.
>
>So I was thinking of doing the whole thing in RPG, and as I'm using
>RPG I would rather use APIs then calling a program using QCMD.
>
>Perhaps this SNA information is stored in a system file somewhere that
>I can just read?
>
>Regards,
>
>Jim Langston
>
>Carsten Flensburg wrote:
> >
> > Jim,
> >
> > I haven't come across any such API yet -- but the WRKNETF has an outfile
> > option that might be useful to you?
> >
> > Best regards,
> > Carsten Flensburg
> >
> > ----- Original Message -----
> > From: <owner-rpg400-l@midrange.com>
> > To: <RPG400-L@midrange.com>
> > Sent: Thursday, January 04, 2001 5:39 PM
> > Subject: WRKNETF API?
> >
> > >
> > >
> > > I'm trying to find the API to give me the same information as the
> > > WRKNETF command.  That is, the list of files sent to a user not yet
> > > received.
> > >
> > > I'm searching though the API list at the Infocenter, but can't seem
> > > to find it.
> > >
> > > Anyone know?
> > >
> > > Regards,
> > >
> > > Jim Langston
>+---
>| This is the RPG/400 Mailing List!
>| To submit a new message, send your mail to RPG400-L@midrange.com.
>| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
>| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
>| Questions should be directed to the list owner/operator: david@midrange.com
>+---

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---