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.
I just want to know if someone out there have experienced running cobol routines from web focus. We have a webfocus reporting server on windows and we are using an eda adaptor to connect to our alpha machine. I can run a regular focus with no problem but I dont know how what to use/syntax for calling a cobol routine. I tried most of the examples from the manual but nothing seems to work. Thanks.This message has been edited. Last edited by: Kerry,
I am running WebFocus 4.3.6 and 5.2.5 and MVS 7.1.1 and 7.2(a).
With this said. I need to know how your environment is set up. At present I am running Webfocus that uses Cobol programs to Update/Insert into multiple DB2 databases and JCL to run other applications on the Mainframe.
So with a little bit more information I can point you in the correct direction.
Regards,
Posts: 117 | Location: US | Registered: February 09, 2004
This is all from so long ago. Are you in a TSO environment on the mainframe?
Try this, it's subtly different - it uses DYNAM ALLOC instead of TSO ALLOC. If I remember correctly, the -? TSO DDNAME command sets the environment variable &DSNAME so that the TSO SUBMIT can run correctly.
-SET &PROC = IF &&MM EQ '01' THEN 'SI920' ELSE 'SI921';
SQL DB2 SET AUTOCOMMIT ON FIN SQL DB2 SET PLAN DB2Named plan -RUN -******************************************************************** -*INVOKE COBOL PROGRAM -********************************************************************
To issue a TSO command such as submit, you need to prefix TSO with a dash.
-TSO SUBMIT(jclfile)
The same goes for any other OS command -DOS... -UNIX...
but as David pointed out - using the DYNAM command should work just fine, and would work from a batch environment as well.This message has been edited. Last edited by: Gizmo,
Windows: WF 7.6.2: SQL Server 2008 R2
Posts: 86 | Location: Chicago | Registered: August 03, 2007