BATCH2 (TCP/IP) - Revision history

JDamon: Accurately numbered the two kinds of BATCH2 programs

2018-11-20T17:06:45Z

Accurately numbered the two kinds of BATCH2 programs

← Older revision		Revision as of 17:06, 20 November 2018
Line 1:		Line 1:
	BATCH2 is a program that allows a stream of commands in a sequential file to be sent to a <var class="product">[[Model 204]]</var> [[Online]], and to save the output from those commands to another sequential file. There are basically two BATCH2 programs:		BATCH2 is a program that allows a stream of commands in a sequential file to be sent to a <var class="product">[[Model 204]]</var> [[Online]], and to save the output from those commands to another sequential file. There are basically two BATCH2 programs:

	#A BATCH2 program written in assembler and provided by Rocket Software that uses CRAM as its transport. Because CRAM is an inter-address space transport, this BATCH2 can only work if the BATCH2 program is running on the same machine and [http://en.wikipedia.org/wiki/LPAR LPAR] as the target Online. This BATCH2 is further described in [[Program Communication facilities#BATCH2\|Program Communication facilities]].		1. A BATCH2 program written in assembler and provided by Rocket Software that uses CRAM as its transport. Because CRAM is an inter-address space transport, this BATCH2 can only work if the BATCH2 program is running on the same machine and [http://en.wikipedia.org/wiki/LPAR LPAR] as the target Online. This BATCH2 is further described in [[Program Communication facilities#BATCH2\|Program Communication facilities]].

	#A BATCH2 program written in C provided by [[Sirius Software]] that uses TCP/IP as its transport. Because TCP/IP allows communication between different machines, there are no restrictions on where the BATCH2 program is relative to the target Online. This is the BATCH2 program that is the subject of this page.		2. A BATCH2 program written in C provided by [[Sirius Software]] that uses TCP/IP as its transport. Because TCP/IP allows communication between different machines, there are no restrictions on where the BATCH2 program is relative to the target Online. This is the BATCH2 program that is the subject of this page.

	<p class="warn"><b>Note:</b> The TCP/IP BATCH2 program is currently unavailable. For more information, [[Contacting Rocket Software Technical Support\|contact Rocket M204 Technical Support]]. </p>		<p class="warn"><b>Note:</b> The TCP/IP BATCH2 program is currently unavailable. For more information, [[Contacting Rocket Software Technical Support\|contact Rocket M204 Technical Support]]. </p>

JAL: add space

2018-06-19T19:45:29Z

add space

← Older revision		Revision as of 19:45, 19 June 2018
Line 1:		Line 1:
	BATCH2 is a program that allows a stream of commands in a sequential file to be sent to a <var class="product">[[Model 204]]</var> [[Online]], and to save the output from those commands to another sequential file. There are basically two BATCH2 programs:		BATCH2 is a program that allows a stream of commands in a sequential file to be sent to a <var class="product">[[Model 204]]</var> [[Online]], and to save the output from those commands to another sequential file. There are basically two BATCH2 programs:

	#A BATCH2 program written in assembler and provided by Rocket Software that uses CRAM as its transport. Because CRAM is an inter-address space transport, this BATCH2 can only work if the BATCH2 program is running on the same machine and [http://en.wikipedia.org/wiki/LPAR LPAR] as the target Online. This BATCH2 is further described in [[Program Communication facilities#BATCH2\|Program Communication facilities]].		#A BATCH2 program written in assembler and provided by Rocket Software that uses CRAM as its transport. Because CRAM is an inter-address space transport, this BATCH2 can only work if the BATCH2 program is running on the same machine and [http://en.wikipedia.org/wiki/LPAR LPAR] as the target Online. This BATCH2 is further described in [[Program Communication facilities#BATCH2\|Program Communication facilities]].

JAL: add link

2017-04-03T14:36:22Z

add link

← Older revision		Revision as of 14:36, 3 April 2017
Line 1:		Line 1:
	BATCH2 is a program that allows a stream of commands in a sequential file to be sent to a <var class="product">[[Model 204]]</var> [[Online]], and to save the output from those commands to another sequential file. There are basically two BATCH2 programs:		BATCH2 is a program that allows a stream of commands in a sequential file to be sent to a <var class="product">[[Model 204]]</var> [[Online]], and to save the output from those commands to another sequential file. There are basically two BATCH2 programs:
	#A BATCH2 program written in assembler and provided by Rocket Software that uses CRAM as its transport. Because CRAM is an inter-address space transport, this BATCH2 can only work if the BATCH2 program is running on the same machine and [http://en.wikipedia.org/wiki/LPAR LPAR] as the target Online.
			#A BATCH2 program written in assembler and provided by Rocket Software that uses CRAM as its transport. Because CRAM is an inter-address space transport, this BATCH2 can only work if the BATCH2 program is running on the same machine and [http://en.wikipedia.org/wiki/LPAR LPAR] as the target Online. This BATCH2 is further described in [[Program Communication facilities#BATCH2\|Program Communication facilities]].

	#A BATCH2 program written in C provided by [[Sirius Software]] that uses TCP/IP as its transport. Because TCP/IP allows communication between different machines, there are no restrictions on where the BATCH2 program is relative to the target Online. This is the BATCH2 program that is the subject of this page.		#A BATCH2 program written in C provided by [[Sirius Software]] that uses TCP/IP as its transport. Because TCP/IP allows communication between different machines, there are no restrictions on where the BATCH2 program is relative to the target Online. This is the BATCH2 program that is the subject of this page.

JAL: add "program unavailable, contact Support" note

2015-11-09T17:10:29Z

add "program unavailable, contact Support" note

← Older revision		Revision as of 17:10, 9 November 2015
Line 2:		Line 2:
	#A BATCH2 program written in assembler and provided by Rocket Software that uses CRAM as its transport. Because CRAM is an inter-address space transport, this BATCH2 can only work if the BATCH2 program is running on the same machine and [http://en.wikipedia.org/wiki/LPAR LPAR] as the target Online.		#A BATCH2 program written in assembler and provided by Rocket Software that uses CRAM as its transport. Because CRAM is an inter-address space transport, this BATCH2 can only work if the BATCH2 program is running on the same machine and [http://en.wikipedia.org/wiki/LPAR LPAR] as the target Online.
	#A BATCH2 program written in C provided by [[Sirius Software]] that uses TCP/IP as its transport. Because TCP/IP allows communication between different machines, there are no restrictions on where the BATCH2 program is relative to the target Online. This is the BATCH2 program that is the subject of this page.		#A BATCH2 program written in C provided by [[Sirius Software]] that uses TCP/IP as its transport. Because TCP/IP allows communication between different machines, there are no restrictions on where the BATCH2 program is relative to the target Online. This is the BATCH2 program that is the subject of this page.

			<p class="warn"><b>Note:</b> The TCP/IP BATCH2 program is currently unavailable. For more information, [[Contacting Rocket Software Technical Support\|contact Rocket M204 Technical Support]]. </p>

	Originally, TCP/IP BATCH2 was developed for [http://en.wikipedia.org/wiki/Unix Unix]. As such, it used Unix-style command-line parameters. TCP/IP BATCH2 was then extended for execution on [http://en.wikipedia.org/wiki/Microsoft_Windows Microsoft Windows] and, finally, for IBM mainframe operating systems [http://en.wikipedia.org/wiki/VM_%28operating_system%29 VM], [http://en.wikipedia.org/wiki/MVS MVS] and, now, [http://en.wikipedia.org/wiki/Z/OS z/OS]).		Originally, TCP/IP BATCH2 was developed for [http://en.wikipedia.org/wiki/Unix Unix]. As such, it used Unix-style command-line parameters. TCP/IP BATCH2 was then extended for execution on [http://en.wikipedia.org/wiki/Microsoft_Windows Microsoft Windows] and, finally, for IBM mainframe operating systems [http://en.wikipedia.org/wiki/VM_%28operating_system%29 VM], [http://en.wikipedia.org/wiki/MVS MVS] and, now, [http://en.wikipedia.org/wiki/Z/OS z/OS]).

JDamon: Removed blank lines in //SYSLIN DD * to eliminate separate boxes for ENTRY CEESTART,NAME BATCH2(R) and the /*,//

2013-10-16T19:00:02Z

Removed blank lines in //SYSLIN DD * to eliminate separate boxes for ENTRY CEESTART,NAME BATCH2(R) and the /*,//

← Older revision		Revision as of 19:00, 16 October 2013
Line 173:		Line 173:
	INCLUDE SIRIUS(BATCH2)		INCLUDE SIRIUS(BATCH2)
	INCLUDE SIRIUS(BATCH2CH)		INCLUDE SIRIUS(BATCH2CH)

	ENTRY CEESTART		ENTRY CEESTART
	NAME BATCH2(R)		NAME BATCH2(R)

	/*		/*
	//		//
	The names of the Sirius libraries (''SIRIUS.LIB'' and ''SIRIUS.LOAD'') and the C runtime libraries (''TCPIP.SEZACMTX'' and ''CEE.SCEELKED'') might need to be changed to match the names used locally.		The names of the Sirius libraries (''SIRIUS.LIB'' and ''SIRIUS.LOAD'') and the C runtime libraries (''TCPIP.SEZACMTX'' and ''CEE.SCEELKED'') might need to be changed to match the names used locally.
	[[Category:Janus TCP/IP Base\|BATCH2 (TCP/IP mainframe program)]]		[[Category:Janus TCP/IP Base\|BATCH2 (TCP/IP mainframe program)]]

JAL at 00:14, 30 October 2012

2012-10-30T00:14:11Z

← Older revision		Revision as of 00:14, 30 October 2012
Line 1:		Line 1:
	BATCH2 is a program that allows a stream of commands in a sequential file to be sent to a [[Model 204]] [[Online]], and to save the output from those commands to another sequential file. There are basically two BATCH2 programs:		BATCH2 is a program that allows a stream of commands in a sequential file to be sent to a <var class="product">[[Model 204]]</var> [[Online]], and to save the output from those commands to another sequential file. There are basically two BATCH2 programs:
	#A BATCH2 program written in assembler and provided by Rocket Software that uses CRAM as its transport. Because CRAM is an inter-address space transport, this BATCH2 can only work if the BATCH2 program is running on the same machine and [http://en.wikipedia.org/wiki/LPAR LPAR] as the target Online.		#A BATCH2 program written in assembler and provided by Rocket Software that uses CRAM as its transport. Because CRAM is an inter-address space transport, this BATCH2 can only work if the BATCH2 program is running on the same machine and [http://en.wikipedia.org/wiki/LPAR LPAR] as the target Online.
	#A BATCH2 program written in C provided by [[Sirius Software]] that uses TCP/IP as its transport. Because TCP/IP allows communication between different machines, there are no restrictions on where the BATCH2 program is relative to the target Online. This is the BATCH2 program that is the subject of this page.		#A BATCH2 program written in C provided by [[Sirius Software]] that uses TCP/IP as its transport. Because TCP/IP allows communication between different machines, there are no restrictions on where the BATCH2 program is relative to the target Online. This is the BATCH2 program that is the subject of this page.

JAL: /* Trusted login */

2012-10-30T00:13:00Z

Trusted login

← Older revision		Revision as of 00:13, 30 October 2012
Line 60:		Line 60:
	===Trusted login===		===Trusted login===
	Another compatibility issue with the CRAM BATCH2 is that CRAM BATCH2 job stream is capable of doing a “trusted login” in the server Online. A trusted login logs on to the Online with the same userid as the userid under which BATCH2 is running. This requires that the same userid be able to run batch jobs and to log into <var class="product">Model 204</var>.		Another compatibility issue with the CRAM BATCH2 is that CRAM BATCH2 job stream is capable of doing a “trusted login” in the server Online. A trusted login logs on to the Online with the same userid as the userid under which BATCH2 is running. This requires that the same userid be able to run batch jobs and to log into <var class="product">Model 204</var>.
	This is typically not much of a problem at sites where an external authorizer such as [http://en.wikipedia.org/wiki/RACF RACF], [http://en.wikipedia.org/wiki/ACF2 ACF2], and Top Secret (by [http://en.wikipedia.org/wiki/Computer_Associates Computer Associates]) because userids for both JES and Model 204 are managed from the same security server.		This is typically not much of a problem at sites where an external authorizer such as [http://en.wikipedia.org/wiki/RACF RACF], [http://en.wikipedia.org/wiki/ACF2 ACF2], and Top Secret (by [http://en.wikipedia.org/wiki/Computer_Associates Computer Associates]) because userids for both JES and <var class="product">Model 204</var> are managed from the same security server.

	A trusted login is usually indicated by a "naked" ''LOGIN'', that is a ''LOGIN'' command with no userid (or anything else) specified:		A trusted login is usually indicated by a "naked" ''LOGIN'', that is a ''LOGIN'' command with no userid (or anything else) specified:
Line 67:		Line 67:
	V		V
	...		...
	With CRAM BATCH2 it is relatively easy to securely validate the userid under which the BATCH2 program is running because BATCH2 and Model 204 are running on the same machine or LPAR and so cross-memory services can be used to retrieve and validate the userid.		With CRAM BATCH2 it is relatively easy to securely validate the userid under which the BATCH2 program is running because BATCH2 and <var class="product">Model 204</var> are running on the same machine or LPAR and so cross-memory services can be used to retrieve and validate the userid.
	For the TCP/IP BATCH2 the picture is somewhat more complicated. While the TCP/IP BATCH2 always passes the userid under which it is running to the Model 204 server, there is no particular reason for Model 204 to trust that the BATCH2 job should be allowed to run as that userid. This is because that BATCH2 might be running on a different machine from the Online and so could, in theory, be a BATCH2 program or BATCH2 impostor that is being used by someone trying to breach security.		For the TCP/IP BATCH2 the picture is somewhat more complicated. While the TCP/IP BATCH2 always passes the userid under which it is running to the <var class="product">Model 204</var> server, there is no particular reason for <var class="product">Model 204</var> to trust that the BATCH2 job should be allowed to run as that userid. This is because that BATCH2 might be running on a different machine from the Online and so could, in theory, be a BATCH2 program or BATCH2 impostor that is being used by someone trying to breach security.

	So, to add a bit of control to TCP/IP BATCH2 trusted login, the userid passed by BATCH2 will only be used for a trusted login if a ''TRUST'' clause was specified for the target IFDIAL port, and that ''TRUST'' clause indicated an IP address or subnet that matches the BATCH client's IP address. The ''TRUST'' keyword on a ''JANUS DEFINE'' for an IFDIAL port must be followed by one or more IP addresses or subnets, separated by an ''AND'' keyword. Up to 16 IP addresses of subnets are allowed in a ''TRUST'' clause.		So, to add a bit of control to TCP/IP BATCH2 trusted login, the userid passed by BATCH2 will only be used for a trusted login if a ''TRUST'' clause was specified for the target IFDIAL port, and that ''TRUST'' clause indicated an IP address or subnet that matches the BATCH client's IP address. The ''TRUST'' keyword on a ''JANUS DEFINE'' for an IFDIAL port must be followed by one or more IP addresses or subnets, separated by an ''AND'' keyword. Up to 16 IP addresses of subnets are allowed in a ''TRUST'' clause.

JALWiccan: 1 revision

2012-10-30T00:09:05Z

1 revision

← Older revision	Revision as of 00:09, 30 October 2012
(No difference)

Dme at 00:08, 30 October 2012

2012-10-30T00:08:55Z

← Older revision		Revision as of 00:08, 30 October 2012
Line 59:		Line 59:
	The single quotes in the OMC values must be doubled because they occur inside single quotes for the job card.		The single quotes in the OMC values must be doubled because they occur inside single quotes for the job card.
	===Trusted login===		===Trusted login===
	Another compatibility issue with the CRAM BATCH2 is that CRAM BATCH2 job stream is capable of doing a “trusted login” in the server Online. A trusted login logs on to the Online with the same userid as the userid under which BATCH2 is running. This requires that the same userid be able to run batch jobs and to log into Model 204.		Another compatibility issue with the CRAM BATCH2 is that CRAM BATCH2 job stream is capable of doing a “trusted login” in the server Online. A trusted login logs on to the Online with the same userid as the userid under which BATCH2 is running. This requires that the same userid be able to run batch jobs and to log into <var class="product">Model 204</var>.
	This is typically not much of a problem at sites where an external authorizer such as [http://en.wikipedia.org/wiki/RACF RACF], [http://en.wikipedia.org/wiki/ACF2 ACF2], and Top Secret (by [http://en.wikipedia.org/wiki/Computer_Associates Computer Associates]) because userids for both JES and Model 204 are managed from the same security server.		This is typically not much of a problem at sites where an external authorizer such as [http://en.wikipedia.org/wiki/RACF RACF], [http://en.wikipedia.org/wiki/ACF2 ACF2], and Top Secret (by [http://en.wikipedia.org/wiki/Computer_Associates Computer Associates]) because userids for both JES and Model 204 are managed from the same security server.

Dme at 14:16, 19 August 2012

2012-08-19T14:16:04Z

← Older revision		Revision as of 14:16, 19 August 2012
Line 180:		Line 180:
	//		//
	The names of the Sirius libraries (''SIRIUS.LIB'' and ''SIRIUS.LOAD'') and the C runtime libraries (''TCPIP.SEZACMTX'' and ''CEE.SCEELKED'') might need to be changed to match the names used locally.		The names of the Sirius libraries (''SIRIUS.LIB'' and ''SIRIUS.LOAD'') and the C runtime libraries (''TCPIP.SEZACMTX'' and ''CEE.SCEELKED'') might need to be changed to match the names used locally.
	[[Category:Janus TCP/IP Base]]		[[Category:Janus TCP/IP Base\|BATCH2 (TCP/IP mainframe program)]]