Joined: 28 Feb 2006 Posts: 6 Topics: 2 Location: India
Posted: Mon Mar 06, 2006 11:16 pm Post subject:
Jaya,
Quote:
Also I find no reason for J1 to pick a constant file from the FTP site and process it again and again.
Once the file is pulled from mailbox by the job J1 it will delete that file from mailbox. Also the mailbox is setup so that it can hold any number of files with the same name but our MVS job will pick up the file that came last and then delete it. So the files will be picked up in the reverse order.
Quote:
what happens if your job J1 aborts due to some outage..
Whether the third party file will be refreshed with the new version or will it wait till you pick the file?
Job J1 is triggered by demand dataset and it uses other DSN to copy the file. So if J1 fails, the file will be available in the mailbox, once the transfer is successful it gets deleted from mailbox.
Quote:
Hence i had suggested you to send a tag file in your JOB J2 to the third party FTP site saying that your job chain J1-> J2 is completed.
Now your third party can proceed to create the next version of file and after that they can send you the post again to trigger your next J1->J2 chain.
It is not possible to send a tag file to mailbox. We need to have a solution in CA7 itself to resolve this issue.
CaptObvious,
Combining Job1 and Job2 has been considered, but since both these steps runs in different production region (by routing it) we cannot have it in same job.
Quote:
what happens if your job J1 aborts due to some outage..
Whether the third party file will be refreshed with the new version or will it wait till you pick the file?
Job J1 is triggered by demand dataset and it uses other DSN to copy the file. So if J1 fails, the file will be available in the mailbox, once the transfer is successful it gets deleted from mailbox.
If i had understood your requirement right, your job J1 is triggered by a demand dataset which you are not using in your job J1 for any purpose.
Once triggered , Your Job J1 GET'S the recent version of the constant file
using some constant FTP cards from mailbox to MVS dataset and processes them. No of demand dataset post = Number of versions in mailbox.
If my assumptions are right, Instead of triggering J1 by the demand dataset for which you have no control, Your job J1 can be run at fixed intervals say 1 hr. Instead of triggering J2 from J1, Use Internal reader to submit J2 from J1.
J1:
Step1: Check for a recent version in mailbox, if found proceed to step 2, else Force J1 to end
step2: If file available, GET the recent version to MVS and delete it in mailbox.
step3: Process the MVS dataset
step4: submit J2 thru INTRDR.
J2:
step1: Process the output of J1
step2: Check for a recent version in mailbox
step3:if found submit J1 thru INTRDR else force J2 to end.
This logic would process all files available as a batch everyhour.
If the ftp cards to get the files from mailbox is not constant, you can LISTCAT them and prepare the dynamic jobs J1 and J2 for every control file and run them parallely if feasible.
If u cannot allow this 1 Hr max leadtime to process your files, Controlling the demand dataset by means of a TAG file is the only option. In our application, many interfaces with unix system that runs many times a day are controlled by the tag file. Unix processing is triggered by our tag file.
Quote:
Quote:
Hence i had suggested you to send a tag file in your JOB J2 to the third party FTP site saying that your job chain J1-> J2 is completed.
Now your third party can proceed to create the next version of file and after that they can send you the post again to trigger your next J1->J2 chain.
It is not possible to send a tag file to mailbox. We need to have a solution in CA7 itself to resolve this issue.
Tag file should be sent to the system which sends you the the post rather than mailbox. I mean , their processing should get triggered by your tag file.
If this doesn't answer your query..It is better that you post your complete requirement and the experts here would give you the optimal design. I feel that you are designing it more complex than required.
Thanks,
Jaya. _________________ "Great spirits have always encountered violent opposition from mediocre minds."
-Albert Einstein
Joined: 28 Feb 2006 Posts: 6 Topics: 2 Location: India
Posted: Wed Mar 08, 2006 9:22 am Post subject:
Hi Jaya,
You have understood the requirements correctly. I guess your suggestion in using the internal reader will work for me.
Quote:
If the ftp cards to get the files from mailbox is not constant, you can LISTCAT them and prepare the dynamic jobs J1 and J2 for every control file and run them parallely if feasible.
Our ftp cards remains the same. So no issue regarding this.
Quote:
If u cannot allow this 1 Hr max leadtime to process your files, Controlling the demand dataset by means of a TAG file is the only option. In our application, many interfaces with unix system that runs many times a day are controlled by the tag file. Unix processing is triggered by our tag file.
There is no need to go for this process since they allowed us to put 1hour lead time.
Big thanks for all of you for the valuable suggestions. Looking forward for you help in future.
All times are GMT - 5 Hours Goto page Previous1, 2
Page 2 of 2
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
