Hi Jim - >I know I can create a never ending job that will check the >last member of the file and compare it against a data queue, >and if the file member is different than the last one received >(which would probably be *blanks) I would then try to allocate >the file until I could, once I could allocate it I would send >it to my other AS/400 then do some cleanup (copy it to another >file name maybe, or just update the data area with the last >member received). > >I really don't want to do this, however, as this never ending job >is going to be eating up CPU cycles checking for the presence of >a new member. And yes, I understand it won't be that much CPU, >but I would rather it was nothing until such time as the file >was actually received. A simple DLYJOB would take care of the CPU problem. Do a DLYJOB DLY(60) to wait 60 seconds; check if an ENDJOB is pending, if so end the job (this will cause the job to end cleanly for an ENDSBS, ENDSYS, or PWRDWNSYS request); then check for the file being received. If the file was not received, loop back to the DLYJOB, otherwise process it and loop back to the DLYJOB. Will there be a new member with a different name each time? Your message implied this, and that would make detecting the file arrival easier. Ken Southern Wine and Spirits of Nevada, Inc. Opinions expressed are my own and do not necessarily represent the views of my employer or anyone in their right mind. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: email@example.com +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.