Focal Point Banner


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.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [CASE-OPENED] Batch FOCUS, MVS platform, release 7.7.03

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[CASE-OPENED] Batch FOCUS, MVS platform, release 7.7.03
 Login/Join
 
Member
posted
Our shop is in the process of upgrading from FOCUS 7.3.2 to release 7.7.03 .


I have basically run into a coding problem in the //SYSIN DD *

We have quite a number of different PDF datasets which contain FEXs separated by department.
A number of our MVS jobs use internal dynamic allocate processes like the following in a separate PDF for easier control of the database allocations.
The DD name for this separate common PDF is
//DYNALOC DD DSN=PFCI.FOCADM.DYNALOC.DATA(XFSAL12),DISP=SHR

here is an example member in //DYNALOC:
________________________________________________SET ALL=PASS
? SET ALL
DYNAM ALLOC FI SALIMGY1 DSN PFC.PCACTU.SALIM.GY1.XFOCUS SHR REUSE
DYNAM ALLOC FI SALIMMY1 DSN PFC.PCACTU.SALIM.MY1.XFOCUS SHR REUSE
DYNAM ALLOC FI SALIMGY2 DSN PFC.PCACTU.SALIM.GY2.XFOCUS SHR REUSE
DYNAM ALLOC FI SALIMMY2 DSN PFC.PCACTU.SALIM.MY2.XFOCUS SHR REUSE
USE SALIMGY1 AS SALIM00
SALIMMY1 AS SALIM00
SALIMGY2 AS SALIM00
SALIMMY2 AS SALIM00
END
________________________________________________
I release what is in SYSIN is not a true FEX but here is my problem with the difference between releases:

//SYSIN DD *
EX ‘XFSAL12 DYNALOC’
EX SALRPT01
FIN

Release 7.3.2 executes:

EX XFSAL12 from //DD DYNALOC DSN………….
EX SALRPT01 from //DD FOCEXEC DSN…………….

Release 7.7.03 results are:

EX 'XFSAL123 DYNALOC'

(FOC227) THE FOCEXEC PROCEDURE CANNOT BE FOUND: 'XFSAL123 DYNALOC'
>
EX SALRPT01
(FOC036) NO DATA FOUND FOR THE FOCUS FILE NAMED: SALIM00

I know the work around. IF at all possible, I do not want to have to copy every menber of our production //DYNALOC to each of the production //FOCEXEC PDF's

then also change all of our production SYSIN *
EX ’XFSAL12 DYNALOC’
statements to EX XFSAL12



Thanks for any other approches that might be easier.

R J Miller

This message has been edited. Last edited by: <Kathryn Henning>,


WebFOCUS 7.7, Windows, PDF, HTML
 
Posts: 5 | Location: Farm Bureau Life Insurance | Registered: December 08, 2004Report This Post
Virtuoso
posted Hide Post
quote:
//DYNALOC DD DSN=PFCI.FOCADM.DYNALOC.DATA(XFSAL12),DISP=SHR

The membername "(XFSAL12)" seems inappropriate in the DD statement -- it does not make sense to search
PFCI.FOCADM.DYNALOC.DATA(XFSAL12),
which is a *member of a partitioned dataset*, for a member named XFSAL12.

So either use
EX DYNALOC
-- direct execution of a sequential dataset -- rather than
EX ’XFSAL12 DYNALOC’

or omit "(XFSAL12)" from the DD statement, so that
EX ’XFSAL12 DYNALOC’
will *search the partitioned dataset* for the XFSAL12 member.
 
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005Report This Post
Member
posted Hide Post
We are running z/OS on the MVS platform


WebFOCUS 7.7, Windows, PDF, HTML
 
Posts: 5 | Location: Farm Bureau Life Insurance | Registered: December 08, 2004Report This Post
Member
posted Hide Post
Thanks j.gross,

I can see that you understand the approach we are taking. Do you use this concept? Which release for FOCUS are you using? I have not yet found an example of the EX 'fex ddname' in the FOCUS 7.7.03 doc.


I actually indicated:

//DYNALOC DD DSN=PFCI.FOCADM.DYNALOC.DATA(XFSAL12),DISP=SHR only to explain where the member is located.

Infact we do have it coded as you suggest...
//DYNALOC DD DSN=PFCI.FOCADM.DYNALOC.DATA,DISP=SHR

and then SYSIN *
EX 'XFSAL12 DYNALOC'


WebFOCUS 7.7, Windows, PDF, HTML
 
Posts: 5 | Location: Farm Bureau Life Insurance | Registered: December 08, 2004Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [CASE-OPENED] Batch FOCUS, MVS platform, release 7.7.03

Copyright © 1996-2020 Information Builders