WorkPath - Revision history

Laura: /* Work File Naming */

2014-09-22T20:18:29Z

Work File Naming

← Older revision		Revision as of 20:18, 22 September 2014
Line 2:		Line 2:

	===Work File Naming===		===Work File Naming===
	Work files other than EDIT work files have the same names they have in the past except their WSID also includes the SESSION ID digit and they are subject to the following WORKPATH enhancement:		(4.2+)Work files other than EDIT work files have the same names they have in the past except their WSID also includes the SESSION ID digit and they are subject to the following WORKPATH enhancement:

	#The fullpath portion of the existing WORKPATH statement is now optional.		#The fullpath portion of the existing WORKPATH statement is now optional.
Line 9:		Line 9:
	WBSPL0211.Margaret.02		WBSPL0211.Margaret.02

	Note that SESSIONID is retained and login_name is inserted with an extra period.		Note that [[SESSIONID]] is retained and [[login_name]] is inserted with an extra period.

	WORKPATH [LOGIN_NAME] (just specify workfile name inclusion)		WORKPATH [LOGIN_NAME] (just specify workfile name inclusion)

Laura: /* 4.2 Update */

2014-09-22T20:17:20Z

4.2 Update

← Older revision		Revision as of 20:17, 22 September 2014
Line 1:		Line 1:
	The '''WorkPath''' [[config]] specification identifies a path location to be used for the [[Business Rules!]] Workfile. This was useful for directing the work path to a RAM disk.		The '''WorkPath''' [[config]] specification identifies a path location to be used for the [[Business Rules!]] Workfile. This was useful for directing the work path to a RAM disk.

	===~~4.2 Update~~===		===Work File Naming===
	Work files other than EDIT work files have the same names they have in the past except their WSID also includes the SESSION ID digit and they are subject to the following WORKPATH enhancement:		Work files other than EDIT work files have the same names they have in the past except their WSID also includes the SESSION ID digit and they are subject to the following WORKPATH enhancement:

Laura at 20:42, 16 October 2013

2013-10-16T20:42:51Z

← Older revision		Revision as of 20:42, 16 October 2013
Line 1:		Line 1:
	The '''WorkPath''' [[config]] specification identifies a path location to be used for the [[Business Rules!]] [[Workfile]]. This was useful for directing the work path to a RAM disk.		The '''WorkPath''' [[config]] specification identifies a path location to be used for the [[Business Rules!]] Workfile. This was useful for directing the work path to a RAM disk.

	===4.2 Update===		===4.2 Update===

Laura at 18:25, 8 April 2013

2013-04-08T18:25:56Z

← Older revision		Revision as of 18:25, 8 April 2013
Line 1:		Line 1:
	The '''WorkPath''' [[config]] specification identifies a path location to be used for the [[Business Rules!]] [[Workfile]]. This was useful for directing the work path to a RAM disk.		The '''WorkPath''' [[config]] specification identifies a path location to be used for the [[Business Rules!]] [[Workfile]]. This was useful for directing the work path to a RAM disk.

			===4.2 Update===
			Work files other than EDIT work files have the same names they have in the past except their WSID also includes the SESSION ID digit and they are subject to the following WORKPATH enhancement:

			#The fullpath portion of the existing WORKPATH statement is now optional.
			#A second optional parameter is supported: [LOGIN_NAME] (case insensitive). This causes all work files (other that EDIT files) to be in the format filenameSESSIONID.login_name.suffix
			For example:
			WBSPL0211.Margaret.02

			Note that SESSIONID is retained and login_name is inserted with an extra period.

			WORKPATH [LOGIN_NAME] (just specify workfile name inclusion)
			- or -
			WORKPATH C:\MYAPP\TMP [LOGIN_NAME] (workpath plus name inclusion)

			Files that are affected by WORKPATH:
			• BRSPOOL - client spool files
			• WBSPL - server spool files
			• PDF
			• SORT workfiles
			• INDEX workfiles
			• Other temporary workfiles that have been opened with wsid

			EDIT work file names are not subject to WORKPATH name specifications. They also do not include WSID or SESSION. BR keeps workfiles separate for the same program name located in different directories, but does NOT attempt to separate multiple EDITing sessions either by the same user or different users.

	====Note====		====Note====

Laura at 18:22, 8 April 2013

2013-04-08T18:22:10Z

← Older revision		Revision as of 18:22, 8 April 2013
Line 1:		Line 1:
	The '''WorkPath''' [[config]] specification identifies a path location to be used for the [[Business Rules!]] [[Workfile]]. This is useful for directing the work path to a [[RAM disk]].		The '''WorkPath''' [[config]] specification identifies a path location to be used for the [[Business Rules!]] [[Workfile]]. This was useful for directing the work path to a RAM disk.

	====Note====		====Note====

Laura: /* Note */

2013-04-08T18:21:14Z

Note

← Older revision		Revision as of 18:21, 8 April 2013
Line 2:		Line 2:

	====Note====		====Note====
	*WorkPath is not available for use with [[~~config~~ (command)]]		*WorkPath is not available for use with [[Config]] (command).
	*WorkPath drivename:\\directory where files will be processed		*WorkPath drivename:\\directory where files will be processed

Laura: Created page with "The '''WorkPath''' config specification identifies a path location to be used for the Business Rules! Workfile. This is useful for directing the work path to a [[R..."

2013-04-04T20:59:25Z

Created page with "The '''WorkPath''' config specification identifies a path location to be used for the Business Rules! Workfile. This is useful for directing the work path to a [[R..."

New page

The '''WorkPath''' [[config]] specification identifies a path location to be used for the [[Business Rules!]] [[Workfile]]. This is useful for directing the work path to a [[RAM disk]].

====Note====
*WorkPath is not available for use with [[config (command)]]
*WorkPath drivename:\\directory where files will be processed

<noinclude>
[[Category:Config]]
<noinclude>