As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you need access to myibi, contact us at firstname.lastname@example.org and provide your corporate email address, company, and name.
Well.... I might be able to help just a little. First of all, that's weird. Seond, though, ERRORS is no doubt a DDNAME pointing to, in the case, a partitioned data set, of which the Holiday file has to be a member.
Try issuing a ? TSO DDNAME command (I think that's the syntax. No longer have a FOCUS/TSO manual). Hopefully, ERRORS is a FOCUS-defined DDNAME. If so, you'll see ERRORS in the output of that command, along with the dataset it points to
Posts: 135 | Location: Portland, OR | Registered: March 23, 2005
We had our own business day routines before they became available in Focus so we do not use the focus business day functions. When I issue a ? tso ddname query I get all the file allocations and the ddname errors points to a concatenation of 2 pds datasets. In our setup the first dataset is focus.errors which I believe comes from focus. The second pds dataset contains our own written business day subroutines.
Hope this helps. Good luck.
FOCUS 7.6 MVS PDF,HTML,EXCEL
Posts: 115 | Location: Chicago, IL | Registered: May 28, 2004
I might be able to help a little here too but the memory is a little rusty. If I'm remembering correctly, to run FOCUS on the mainframe, it has to be started as a 'task'. This is something system people typically do. To start the 'task', you need JCL - that stands for Job Control Language and it's like DOS is to the PC. I'd venture a guess that the ERRORS file you're looking for is referenced there. I'm very surprised the ? TSO DDNAME did not find this. Find out who installed FOCUS on your mainframe. They may be able to assist you.
Data Migrator 5.3, 7.1, 7.6 WebFOCUS 7.1, 7.6, 7.7 SQL Server, Oracle, DB2 Windows
Under MVS Errors is a PDS Library data set. in most installations it a system data set, and owned by the people who control the operating system and the FOCUS insatalltion. This makes it difficult to get a member added for the workday rountine.
Jim Morrow Web Focus 7.6.10 under Windows 2003 MVS 7.3.3
Thanks everyone. I'm thinking this is way beyond something I would be able to do. I guess I'll just have to keep updated the schedules manually until we upgrade again.
On another note, has anyone had the problem when you make a change to a schedule (like change the run date), the report automatically runs when you save the change instead of waiting to run on the next run date?
Posts: 34 | Location: Chicago, IL | Registered: September 02, 2004