One of the most used app in JDE is WSJ or Work with Submitted Jobs or
P986116. Irrespective of our roles in JDE we use this app to check for
the job statuses that run on the servers. This is one of the trickiest
things to configure when you have a split system and are going through a
migration which involves changes in the hostnames of the parent
servers. Lets have a sneek peek of what goes on behind the scene when
WSJ is executed from a client pc.
1. P986116 gets executed and it lists the Data Sources from F98611 (Data Source Master).
2. When you hit on Find on P986116 the app queries the System.F98611 for all the Server type (SVR) data sources which are then returned on the grid.
3. Now once the data source is selected, the system sets the OMSRVR from the F98611 record as the hostname to be serached in SVM.F986110.
4. Status of the jobs are written in the SVM Job Control Status Master (F986110).
5. System then queries SVM.F986110 pulling up records for which the hostname matches the SVR of the DataSource picked.
If a Unix migration is being attempted care must be taken that the hostname of the machine matches the exact case of the OMSRVR field in F98611. In case of systems with muliple Enterprise servers the SYS.F98611 becomes the spine of everything working together. If there are multiple SYS’s then all of them need to be updated such that a user can query status of his job across the environments. Unless the SYS.F98611 are properly updated the DataSource changes will not show up and users will not be able to check job statuses of say, a job running in PD while he is logged in to QA.
1. P986116 gets executed and it lists the Data Sources from F98611 (Data Source Master).
2. When you hit on Find on P986116 the app queries the System.F98611 for all the Server type (SVR) data sources which are then returned on the grid.
3. Now once the data source is selected, the system sets the OMSRVR from the F98611 record as the hostname to be serached in SVM.F986110.
4. Status of the jobs are written in the SVM Job Control Status Master (F986110).
5. System then queries SVM.F986110 pulling up records for which the hostname matches the SVR of the DataSource picked.
If a Unix migration is being attempted care must be taken that the hostname of the machine matches the exact case of the OMSRVR field in F98611. In case of systems with muliple Enterprise servers the SYS.F98611 becomes the spine of everything working together. If there are multiple SYS’s then all of them need to be updated such that a user can query status of his job across the environments. Unless the SYS.F98611 are properly updated the DataSource changes will not show up and users will not be able to check job statuses of say, a job running in PD while he is logged in to QA.
No comments:
Post a Comment