As Far as my Vision goes When a Program tries to use a dataset which is migrated, OS automatically takes care to get the dataset from TAPE to disk.
But unfortunately we got this problem today in production the dataset migrated and program is hanged and i noticed one of the input file is still migrated even Program started Running.So i have given a Manual HRECALL and job went fine.
I Just to make sure that this problem will not occur next time in production.
Thats why is there any way to check whether dataset migrated from JCL/Program.If so, how...?
Joined: 03 Nov 2004 Posts: 21 Location: NOIDA, India
I am not sure if there is something that could check for the migration state of the dataset in JCL. As u correctly pointed that a migrated dataset gets automatically recalled when the dataset is needed.
But sometimes what happens is,if the dataset is large enough (more data) or to say lots of datasets recalled at the same time then there is a situation of bottle neck and it starts taking more time. So the job waits and waits and may even abend for time out.
So one temporary soln could be ...for example if this job is a daily run. I would say its worth not migrating this dataset. So u could have the dataset with a management class (MGMTCLASS) something that would not migrate it at all.
Its quite possible its not a feasible soln but i am just trying to provide u a soln that could be useful in the scenerio i have mentioned.