 | This article is rated C-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||
| ||||||||||||||
This doesn't tell me much at all. Mainframe computers from what era? Running what operating system? Is this protocol still used anywhere? 74.78.116.93 (talk) 00:30, 9 January 2009 (UTC)
- Remote job entry facilities were available in operating systems from the 1960's to the present. The specific term RJE originally referred to the RJE component of OS/360. The protocol that the RJE component of OS/360 used to communicate with programmable work stations was not used by any subsequent software that I am aware of. The protocol used for RJE by the IBM 2770, 2780 and 3780 is still supported by JES2 and JES3 in z/OS and by RSCS in z/VM. The multi-leaving protocol introduced by HASP II is supported by JES2, JES3 and RSCS. I'm not sure about z/VSE.
- I suspect that Bull and Unisys still support some form of RJE, but have no idea of the protocols. Shmuel (Seymour J.) Metz Username:Chatul (talk) 16:12, 21 August 2012 (UTC)
Requested move
edit- The following discussion is an archived discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review. No further edits should be made to this section.
The result of the move request was: moved per request. Favonian (talk) 19:21, 28 August 2012 (UTC)
Remote Job Entry → Remote job entry –
The article is framed as generic. The specific, which probably does deserve to retain the caps, is given as an example in the first section: "Remote Job Entry (RJE) is also the name of an OS/360 component[1] that provided RJE services."
Per WP:MOSCAPS ("Wikipedia avoids unnecessary capitalization") and WP:TITLE, this is a generic, common term, not a propriety or commercial term, so the article title should be downcased. In addition, WP:MOSCAPS says that a compound item should not be upper-cased just because it is abbreviated with caps. Lowercase will match the formatting of related article titles. Tony (talk) 04:42, 21 August 2012 (UTC)
- Support as a no-brainer per WP:MOSCAPS. Would be an easy non-admin move (as would many, many others) if the damned bot hadn't added the template.--ukexpat (talk) 19:57, 22 August 2012 (UTC)
- I tried, but it wouldn't let me. Tony (talk) 11:00, 23 August 2012 (UTC)
- It requires an admin to do the move because of the subsequent edit by the bot.--ukexpat (talk) 14:02, 23 August 2012 (UTC)
- I tried, but it wouldn't let me. Tony (talk) 11:00, 23 August 2012 (UTC)
- The above discussion is preserved as an archive of a requested move. Please do not modify it. Subsequent comments should be made in a new section on this talk page or in a move review. No further edits should be made to this section.
Timeline?
editDoes anybody have dates for when the various RJE nd NJE applications supported each of the protocols? Shmuel (Seymour J.) Metz Username:Chatul (talk) 20:58, 3 December 2019 (UTC)
HASP Multi-leaving is not full duplex over BSC
edit@Peter Flass: The HASP Multi-leaving protocol[1] over BSC[2] retains the half duplex character of BSC. This remains true for NJE[3] over BSC.
References
- ^ "MULTI-LEAVING in BSC/RJE" (PDF). OS/VS2 HASP II Version 4 Logic Program Number 370H-TX-001 VS2 SVS Release 1.7 (PDF) (First ed.). IBM. March 1973. p. 161. GY27-7255-0.
{{cite book}}:|work=ignored (help) - ^ General Information - Binary Synchronous Communications (PDF) (First ed.). IBM. A27-3004-0.
{{cite book}}:|work=ignored (help) - ^ "Providing BSC and CTC Protocols for Stream Control" (PDF). Network Job Entry (NJE) Formats and Protocols (PDF). IBM. September 30, 2021. p. 161. SA32-0988-50.
{{cite book}}:|work=ignored (help)