Client Current Dir - Revision history

Gordon.dye at 20:13, 10 November 2019

2019-11-10T20:13:08Z

← Older revision		Revision as of 20:13, 10 November 2019
Line 5:		Line 5:
	This path will be passed to [[Windows]] as the [[Starting Directory]] during subsequent client [[shell]] calls. This statement can be specified in the configuration file and also can be called dynamically with the [[CONFIG]] command.		This path will be passed to [[Windows]] as the [[Starting Directory]] during subsequent client [[shell]] calls. This statement can be specified in the configuration file and also can be called dynamically with the [[CONFIG]] command.

	The 'SYNC' value indicates keep the client in sync with the server. Each time a CD is performed on the server a corresponding CD is issued on the client. ''This requires that the second parameter of the BR drive statements match the ~~Samba~~ drive mappings.''		The 'SYNC' value indicates keep the client in sync with the server. Each time a CD is performed on the server a corresponding CD is issued on the client. ''This requires that the second parameter of the BR drive statements match the server operating system drive mappings.''

	If a Client_Current_Dir statement is subsequently executed which specifies a directory (instead of SYNC) then no further attempt will be made to correlate client and server current directories.		If a Client_Current_Dir statement is subsequently executed which specifies a directory (instead of SYNC) then no further attempt will be made to correlate client and server current directories.

	If Client_Current_Dir statement specifies SYNC, then a CD is performed on the client to match the current ~~directory on the current drive on the~~ server, ~~at the point where~~ the config statement is processed.		If Client_Current_Dir statement specifies SYNC, then a CD is performed on the client to match the current server path, when the config statement is processed.

	From that point on all subsequent server CD commands (done in BR) are mirrored on the client, for example:		From that point on all subsequent server CD commands (done in BR) are mirrored on the client, for example:
Line 15:		Line 15:
	CLIENT_CURRENT_DIR SYNC		CLIENT_CURRENT_DIR SYNC

	To use this feature~~, the Samba (or Vision, etc.)~~ drive letter must map to the ~~same~~ logical drive letter (first ~~DRIVE statement~~ parameter)~~, as it does~~ in the DRIVE statement, and the root directory ~~on such Samba drives~~ must be the directory ~~that is pointed to by~~ the second parameter of the DRIVE ~~statements on the server~~.		To use this feature any OS drive letter specified in a CD command must map to the logical drive letter (first parameter) in the corresponding DRIVE statement, and the server root directory (as viewed by the client) must be the starting directory of the path specified in the second parameter of the DRIVE statement.

	For example, let's say a Linux server has a path /wrk/user/br/ that contains the application, and if Samba defines /wrk/~~user~~ as the root directory on drive J. Then the corresponding DRIVE statement should be:		For example, let's say a Linux server has a path /wrk/user/br/ that contains the application, and Samba defines /wrk/ as the root directory on drive J. Then in this case the client sees "user" as the first subdirectory below the root, and the corresponding DRIVE statement should be:

	DRIVE J:,/wrk/~~user~~,x,\BR		DRIVE J:,/wrk/,x,\user\br

	~~Then if~~ the ~~BRCONFIG.SYS file contained "CLIENT_CURRENT_DIR SYNC", then a CD \~~BR~~\DATA would set the~~ current directory to ~~DATA on both the client and the server~~.		This sets the BR current working directory to \user\br.

	This is useful for COPY filename @:filename2 commands (copies to the client). Note that correlation of Samba drives with the second parameter of BR Drive statements is also useful for ODBC and SPOOLCMD purposes.		Then if the BRCONFIG.SYS file contained "CLIENT_CURRENT_DIR SYNC", a CD DATA would set the current BR directory to J:\user\br\data on both the client and the server.

			This is useful for COPY filename @:filename2 commands (copies to and from the client). Note that correlation of Samba drives with the second parameter of BR Drive statements is also useful for ODBC and SPOOLCMD purposes.

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

Gordon.dye at 11:15, 18 September 2019

2019-09-18T11:15:14Z

← Older revision		Revision as of 11:15, 18 September 2019
Line 3:		Line 3:
	CLIENT_CURRENT_DIR full_pathname_on_client \| SYNC		CLIENT_CURRENT_DIR full_pathname_on_client \| SYNC

	This path will be passed to [[Windows]] as the [[Starting Directory]] during subsequent client [[shell]] calls. This statement can also be called dynamically with the [[CONFIG]] command.		This path will be passed to [[Windows]] as the [[Starting Directory]] during subsequent client [[shell]] calls. This statement can be specified in the configuration file and also can be called dynamically with the [[CONFIG]] command.

	The 'SYNC' value indicates keep the client in sync with the server. Each time a CD is performed on the server a corresponding CD is issued on the client. ''This requires that the second parameter of the BR drive statements match the Samba drive mappings.''		The 'SYNC' value indicates keep the client in sync with the server. Each time a CD is performed on the server a corresponding CD is issued on the client. ''This requires that the second parameter of the BR drive statements match the Samba drive mappings.''
Line 9:		Line 9:
	If a Client_Current_Dir statement is subsequently executed which specifies a directory (instead of SYNC) then no further attempt will be made to correlate client and server current directories.		If a Client_Current_Dir statement is subsequently executed which specifies a directory (instead of SYNC) then no further attempt will be made to correlate client and server current directories.

	If Client_Current_Dir statement specifies @S, then a CD is performed on the client to match the current directory on the current drive on the server, at the point where the config statement is processed.		If Client_Current_Dir statement specifies SYNC, then a CD is performed on the client to match the current directory on the current drive on the server, at the point where the config statement is processed.

	From that point on all subsequent server CD commands (done in BR) are mirrored on the client, for example:		From that point on all subsequent server CD commands (done in BR) are mirrored on the client, for example:

	CLIENT_CURRENT_DIR @S		CLIENT_CURRENT_DIR SYNC

	To use this feature, the Samba (or Vision, etc.) drive letter must map to the same logical drive letter (first DRIVE statement parameter), as it does in the DRIVE statement, and the root directory on such Samba drives must be the directory that is pointed to by the second parameter of the DRIVE statements on the server.		To use this feature, the Samba (or Vision, etc.) drive letter must map to the same logical drive letter (first DRIVE statement parameter), as it does in the DRIVE statement, and the root directory on such Samba drives must be the directory that is pointed to by the second parameter of the DRIVE statements on the server.
Line 21:		Line 21:
	DRIVE J:,/wrk/user,x,\BR		DRIVE J:,/wrk/user,x,\BR

	Then if the BRCONFIG.SYS file contained "CLIENT_CURRENT_DIR @S", then a CD \BR\DATA would set the current directory to DATA on both the client and the server.		Then if the BRCONFIG.SYS file contained "CLIENT_CURRENT_DIR SYNC", then a CD \BR\DATA would set the current directory to DATA on both the client and the server.

	This is useful for COPY filename @:filename2 commands (copies to the client). Note that correlation of Samba drives with the second parameter of BR Drive statements is also useful for ODBC and SPOOLCMD purposes.		This is useful for COPY filename @:filename2 commands (copies to the client). Note that correlation of Samba drives with the second parameter of BR Drive statements is also useful for ODBC and SPOOLCMD purposes.

	~~The CONFIG CLIENT_CURRENT_DIR statement can now be issued dynamically.~~

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

Gordon.dye at 03:31, 18 September 2019

2019-09-18T03:31:20Z

← Older revision		Revision as of 03:31, 18 September 2019
Line 1:		Line 1:
	The '''Client_Current_Dir''' [[config]] specification.		The '''Client_Current_Dir''' [[config]] specification.

	~~Client_Current_Dir(~~full_pathname_on_client~~) / @S~~		CLIENT_CURRENT_DIR full_pathname_on_client \| SYNC

	This path will be passed to [[Windows]] as the [[Starting Directory]] during subsequent client [[shell]] calls. This statement can also be called dynamically with the [[CONFIG]] command.		This path will be passed to [[Windows]] as the [[Starting Directory]] during subsequent client [[shell]] calls. This statement can also be called dynamically with the [[CONFIG]] command.

	The '@S' value ~~specifies to~~ keep the client in sync with the server. Each time a CD is performed on the server a corresponding CD is issued on the client. This requires that the second parameter of the BR drive statements match the Samba drive mappings.		The 'SYNC' value indicates keep the client in sync with the server. Each time a CD is performed on the server a corresponding CD is issued on the client. ''This requires that the second parameter of the BR drive statements match the Samba drive mappings.''

	If a Client_Current_Dir statement is subsequently executed which specifies a directory (instead of @S) then no further attempt will be made to correlate client and server current directories.		If a Client_Current_Dir statement is subsequently executed which specifies a directory (instead of SYNC) then no further attempt will be made to correlate client and server current directories.

	If Client_Current_Dir statement specifies @S, then a CD is performed on the client to match the current directory on the current drive on the server, at the point where the config statement is processed.		If Client_Current_Dir statement specifies @S, then a CD is performed on the client to match the current directory on the current drive on the server, at the point where the config statement is processed.
Line 13:		Line 13:
	From that point on all subsequent server CD commands (done in BR) are mirrored on the client, for example:		From that point on all subsequent server CD commands (done in BR) are mirrored on the client, for example:

	~~Client_Current_Dir~~ @S		CLIENT_CURRENT_DIR @S

	To use this feature, the Samba (or Vision, etc.) drive letter must map to the same logical drive letter (first DRIVE statement parameter), as it does in the DRIVE statement, and the root directory on such Samba drives must be the directory that is pointed to by the second parameter of the DRIVE statements on the server.		To use this feature, the Samba (or Vision, etc.) drive letter must map to the same logical drive letter (first DRIVE statement parameter), as it does in the DRIVE statement, and the root directory on such Samba drives must be the directory that is pointed to by the second parameter of the DRIVE statements on the server.

Laura: Created page with "The '''Client_Current_Dir''' config specification. Client_Current_Dir(full_pathname_on_client) / @S This path will be passed to Windows as the [[Starting Directory]..."

2013-05-07T15:57:55Z

Created page with "The '''Client_Current_Dir''' config specification. Client_Current_Dir(full_pathname_on_client) / @S This path will be passed to Windows as the [[Starting Directory]..."

New page

The '''Client_Current_Dir''' [[config]] specification.

Client_Current_Dir(full_pathname_on_client) / @S

This path will be passed to [[Windows]] as the [[Starting Directory]] during subsequent client [[shell]] calls. This statement can also be called dynamically with the [[CONFIG]] command.

The '@S' value specifies to keep the client in sync with the server. Each time a CD is performed on the server a corresponding CD is issued on the client. This requires that the second parameter of the BR drive statements match the Samba drive mappings.

If a Client_Current_Dir statement is subsequently executed which specifies a directory (instead of @S) then no further attempt will be made to correlate client and server current directories.

If Client_Current_Dir statement specifies @S, then a CD is performed on the client to match the current directory on the current drive on the server, at the point where the config statement is processed.

From that point on all subsequent server CD commands (done in BR) are mirrored on the client, for example:

Client_Current_Dir @S

To use this feature, the Samba (or Vision, etc.) drive letter must map to the same logical drive letter (first DRIVE statement parameter), as it does in the DRIVE statement, and the root directory on such Samba drives must be the directory that is pointed to by the second parameter of the DRIVE statements on the server.

For example, let's say a Linux server has a path /wrk/user/br/ that contains the application, and if Samba defines /wrk/user as the root directory on drive J. Then the corresponding DRIVE statement should be:

DRIVE J:,/wrk/user,x,\BR

Then if the BRCONFIG.SYS file contained "CLIENT_CURRENT_DIR @S", then a CD \BR\DATA would set the current directory to DATA on both the client and the server.

This is useful for COPY filename @:filename2 commands (copies to the client). Note that correlation of Samba drives with the second parameter of BR Drive statements is also useful for ODBC and SPOOLCMD purposes.

The CONFIG CLIENT_CURRENT_DIR statement can now be issued dynamically.

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