... or you could APP HOLD it to a folder in your APP PATH and then WF will find it.

T

and BASEAPP is always in your application path...

According to iWay Server Administration for UNIX, Windows, OpenVMS, OS/400, OS/390, and z/OS V5.3.2 > Accessing Application Files > Controlling the APP Environment (WF 5.3.2) there is no APP HOLD command, there is the APP HOLDMETA command and the APP HOLDDATA command.

If I use APP HOLD or APP HOLDMETA + APP HOLDDATA to save the master and data file, I still need to issue the FILEDEF command in another session to read the HOLD file - the APP HOLD commands will find the Master, but not the data - which I think is ridiculous.

Program 1a

APP HOLD BASEAPP
-RUN
 
TABLE FILE CAR
PRINT
*
ON TABLE HOLD AS HOLDCAR1
END
-RUN

Program 2a

APP HOLD BASEAPP
-RUN
 
TABLE FILE HOLDCAR1
PRINT
*
END
-RUN

Program 1b

APP HOLDMETA BASEAPP
APP HOLDDATA BASEAPP
-RUN
 
TABLE FILE CAR
PRINT
*
ON TABLE HOLD AS HOLDCAR1
END
-RUN

Program 2b

APP HOLDMETA BASEAPP
APP HOLDDATA BASEAPP
-RUN
 
TABLE FILE HOLDCAR1
PRINT
*
END
-RUN

Francis,

The APP HOLD, APP HOLDDATA and APP HOLDMETA are used to direct the hold files not to allow WF to find them. So within the 2a and 2b programs the commands are superfluous.

If you change your programs to HOLD FORMAT FOCUS or XFOCUS then WF should find them OK providing that you directed them to an APP folder within your path. But if you leave them as is then they are basically FTM files for which you generally require a filedef unless that is taken care of within the master (as pointed out by TS).

T

Francis is right. I nevered noticed this before but when you issue an 'APP HELP' command to list all the APP commands, 'APP HOLD ...' is not listed. However, it seems to work OK. I am using WF 713.

Interesting.

I wish I was right in expecting the APP HOLD command to find the recently created HOLD file. After all, you don't have to issue a FILEDEF command to create the file, you shouldn't have to to read it. Since ftm is assumed as the suffix when creating the file, why can't it be assumed when reading the file?

It does this with the master without any trouble.

Francis,

It sounds like you need to submit a new feature request for this to see what IBI would say. The FILEDEF is automatically done for you when CREATING the HOLD file. That's why you do not need to issue the FILEDEF when creating a HOLD file. However, i'm probably just preaching to the choir (talking to someone who already knows this).

Here's my input.

There are several way to get the file allocated to a session so that WebFOCUS will find the data.

1.) Add a FILEDEF in the server's global profile.
2.) Add a FILEDEF in each focexec that needs to access the file.
3.) Use the APP to perform the FILEDEF in step 1 or 2 above.
4.) MODIFY the saved master file description and add the DATASET attribute to it.

I personally fill that option 4 would be the best, because to really make the master file description useful you need to add (TITLES, DESCTIPTIONS, a REMARK, and in your case the DATASET attribute). This also will not allocated the file unless it is needed. 1.) If you put the FILEDEF in the server's global profile everyone is allocating it even if it is not needed. 2.) putting the FILEDEF in each of the focexecs that need it is too much work and maintance could turn into a bear. 3.) same as reasons 1, and 2.

The benefit of using your own FILEDEF is that you can use the same master file for different files if they are the same layout, say if you have different files for different weeks, months, or years and you want to allocate it base on what the user selects.

Hope this give everyone some insite.

Have a WebFOCUS Day