Tuesday, October 9, 2007

Telecommuting


Telecommuting, e-commuting, e-work, telework, working at home (WAH), or working from home (WFH) is a work arrangement in which employees enjoy limited flexibility in working location and hours. In other words, the daily commute to a central place of work is replaced by telecommunication links. Many work from home, while others, occasionally also referred to as nomad workers utilize mobile telecommunications technology to work from coffee shops or myriad other locations. Telework is a broader term, referring to substituting telecommunications for any form of work-related travel, thereby eliminating the distance restrictions of telecommuting.[1] All telecommuters are teleworkers but not all teleworkers are telecommuters. A frequently repeated motto is that "work is something you do, not something you travel to".[2] A successful telecommuting program requires a management style which is based on results and not on close scrutiny of individual employees. This is referred to as management by objectives as opposed to management by observation. The terms telecommuting and telework were coined by American Jack Nilles in 1973.[3]
Long distance telework is facilitated by such tools as virtual private networks, videoconferencing, and Voice over IP. It can be efficient and useful for companies as it allows staff and workers to communicate over a large distance, saving significant amounts of travel time and cost. As broadband Internet connections become more commonplace, more and more workers have enough bandwidth at home to use these tools to link their home office to their corporate intranet and internal phone networks.

Job Entry Subsystem 2/3


IBM's MVS and z/OS operating systems use a job entry subsystem (JES) to receive jobs into the operating system, schedule them for processing by MVS or z/OS, and to control their output processing.
There are two versions of the job entry subsystem concept, JES2 and JES3. The two systems have very little in common, and in fact jobs written to run on one usually require small Job Control Language changes before they can be run on the other.
JES2 (Job Entry Subsystem 2) is descended from HASP, the Houston Automated Spooling Program, developed by the programmers of IBM as self-initiative and eventually owned and supported by IBM for NASA in the mid 1960s. JES3 (Job Entry Subsystem 3) is similarly descended from the Attached Support Processor (ASP), which was IBM's initially-preferred system for OS/360 "unit record I/O". In the 1970s a notable installation of ASP was at Princeton University controlling an IBM 360/91 mainframe.
JES3 has more network style dependency than JES2; as networking and inter-system dependencies have developed, this has become more practical than the single platform environment and single task processes that JES2 addresses.
HASP is defined as: a computer program that provides supplementary job management, data management, and task management functions such as: scheduling, control of job flow, and spooling. HASP remains within JES2 subsystem as the prefix of most module names and the prefix of all messages sent by JES to the operator. JES2 is a functional extension of the HASP II program that receives jobs into the system and processes all output data produced by the job.
So, what does all that mean? Simply stated, JES is a task that runs under MVS which provides the necessary functions to get jobs into, and output out of, the MVS system, and to control the scheduling of their execution. It is designed to provide efficient spooling, scheduling, and management facilities for the MVS operating system. But none of this explains why MVS needs JES. Basically, by separating job processing into a number of tasks, MVS operates more efficiently. At any point in time, the computer system resources are busy processing the tasks for individual jobs, while other tasks are waiting for those resources to become available. In its most simple view, MVS divides the management of jobs and resources between the JES and the base control program of MVS. In this manner, the JES manages jobs before and after running the program; the base control program manages them during processing.