NIPS(ID:5377/nip001)for NMCS INFORMATION PROCESSING SYSTEM According to Sibley (1980) the very first such system to have special data types for lat/long. "The ideas of NIPS (1969) included data types for latitude and longitude with operators like: "find the vehicles within X miles of vehicle Y". " Places Related languages
References: NATIONAL MILITARY COMMAND SYSTEM/NIPS Background. The NMCS Information Processing System (NIPS/360) is in essence the Formatted File System (FFS) converted to the IBM 360/50 computer system and operational under Operating System 360/Option 2. Historically, the FFSs began with the SAC 438L system on the IBM 7090 in 1961. The NIPS predecessor on the IBM 1410 was created in 1963 to satisfy the mission of a Naval Fleet Intelligence Center. Since then the system has been employed at several intelligence centers and commands throughout the world. Basically, the system has evolved in two separate communities: Command and Control, and Intelligence. The Intelligence system (IDHS FFS) has emphasized efficient processing capabilities and improved output options for their many volumed data sources. On the other hand, the Command and Control system (NIPS) has expanded logical file maintenance, improved the query language, and built an on-line retrieval mechanism. Both the second-generation FFS systems operate under the modified 1410 operating system OPSYS (1410-PR-155). The 1410 FFS is being converted to an S/360 model 50H (eight magnetic tape drives, two 2311 discs, one 2394 disc, 2260/1053, and associated card/read/punch printer equipment) in two primary phases. Phase I components include file structuring, file maintenance, retrieval and sort, output, remote inquiry processing, system formatted output, and necessary utilities. Included in Phase II are expanded file maintenance including multifile capabilities, file revision, on-line update, as well as additional components and utilities. The target date for the operational capabilities was January 1968, for Phase I and June 1968, for Phase II. Summary of Capabilities. NIPS/360 is a general-purpose file handling system operating under O/S 360 and performing the traditional functions of structuring, maintaining, revising, and retrieving from a set of data files. While maintaining a high degree of external compatibility with its 1410 predecessor, the internal processing methods have been modified to exploit the capabilities of the third-generation hardware S/360 and of operating system O/S 360. Adhering to the strict O/S 360 programming conventions for communication, base register usage, linkage, etc., the conversion is being done using the COBOL language down to the subroutine level of software. At the subroutine level, either COBOL or assembly language will be used depending on which is necessary to efficiently utilize O/S 360 software and S/360 hardware capabilities. Compatibility with the existing 1410 FFS system was a major design criterion which is being achieved through the ability to use existing FFS control cards, query and summary decks, file maintenance decks, and analyst's procedures. Specific Features. The new system does much to alleviate the physical restrictions of the old system. Specifically, the physical size restriction of a logical record to 2701 characters has been relieved by making each individual group instance a physical record. However, because of compatibility requirements, some of the logical shortcomings are still apparent in the system. In the new system, each File Format Table (FFT is the computer form of the data description or dictionary) will be stored with its file. Thus the NIPS files will be "self-describing" and no longer have a physical remote file description which can easily be misplaced or lost. This should be a major factor in making the transfer of data possible among various installations and is an important development. The S/360 NIPS is primarily a direct access oriented system utilizing the capabilities of the disk through the Index Sequential Access Method (ISAM) of O/S 360. The query language for NIPS, called RASP (Retrieval and Sort Processor) is a good example of its kind. Figure 1 shows the rules for the IF clause which illustrates the POL-like structure and the wide variety of alternatives possible. (1) full exploitation of the S/360 hardware and its related Operating System, providing device independence; (2) the efficiency of disk-resident data files; (3) the flexibility of an open-ended record structure; (4) the simplicity of easy-to- use English-like control language; and (5) the power of more detailed control parameters available to the user who wishes to analyze a problem in depth. in Computer Program Abstracts Cumulative Issue July 15, 1969 -- July 15, 1971 view details in Computer Program Abstracts Cumulative Issue July 15, 1969 -- July 15, 1971 view details in [ACM] ACM Computing Surveys (CSUR) 8(1) March 1976 view details Resources
|