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.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
Is your operating system z/os, sometimes a SOC4 results when it really is a data overflow of secondary extents no space issue. Or just allocating it in general. If a GDG, you might want to adjust the size of the new dataset in your job being submitted, rather than the defaults on the gdg.
Leah
Posts: 1317 | Location: Council Bluffs, IA | Registered: May 24, 2004
You are Correct our system is Z/OS. My output dataset is not GDG. It is just a Flat File with VB format. I will Change the output dataset spaces and give it a shot and let you know what I get.
The problem is sometime the job ran without any ABEND, it is happening in the early morning when the users run this job. Approximately 50 users will run this job almost same time. Some users are having problem with SOC4 and some are able to get the Data without any problem.
I have also added one extra step with Repro to copy the GDG into Dataset for each user. Still didn't work.
I will give it another try and let you know.
Thanks a lot
Posts: 6 | Location: Toronto. | Registered: January 31, 2007
I just want to say THANK YOU for everyone who helped me on this Issue.
This Problem was temporarily solved. We are working with IBM to solve this problem permanently.
The cause of this problem is due to a recent upgrade to the Z/OS CPU’s, these upgrade has been done to Couple of CPU’s in the Z/OS.
Apparently there was glitch in the upgrade that let to this problem.
We are forcing all the jobs to run in the CPU's that are not upgraded. So we are using small patch in the JCL to Force it to a CPU's that are not upgraded. Hopefully we will solve this issue permanently.
Thanks again for all the Experts who helped me on this Issue. I really appreciate your Help.
Thank you
Posts: 6 | Location: Toronto. | Registered: January 31, 2007