Search NASA⌕ Search

SEARCH · Search NASA

Results for “JCL”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

17 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS1987

IBM JCL made easy by means of ISPF dialog application

An interactive cathode ray tube (CRT) terminal application has been developed which automatically generates the job control language (JCL) and submits NASTRAN batch jobs at an IBM mainframe installation. The relevant parameters for each NASTRAN batch job are stored in a table. Once a table entry is defined, the corresponding NASTRAN batch job may be submitted as often as desired with a minimum of keystrokes. For most users, there is no need for any knowledge of JCL.

Cooper, Charles E.↗
NASA NTRS1983

Basic JCL for the CRAY-1 operating system (COS) with emphasis on making the transition from CDC 7600/SCOPE

Users of the CDC 7600 at Ames are assisted in making the transition to the CRAY-1. Similarities and differences in the basic JCL are summarized, and a dozen or so examples of typical batch jobs for the two systems are shown in parallel. Some changes to look for in FORTRAN programs and in the use of UPDATE are also indicated. No attempt is made to cover magnetic tape handling. The material here should not be considered a substitute for reading the more conventional manuals or the User's Guide for the Advanced Computational Facility, available from the Computer Information Center.

Howe, G.↗
NASA NTRS2013

JCL Implementation On A Human Spaceflight Program

Joint Confidence Level (JCL) analysis focuses on the integration of traditionally stove-piped programmatic components (schedule, cost and risk) to establish projected resource and schedule requirements at various confidence levels and to identify programmatic cost and schedule risk drivers. SLS Program consists of multiple Prime Contractors managed by independent SLS Elements which are integrated using SE&I and Program Management. SLS further integrates with GSDO and MPCV through ESD integrated working groups.

Kulpa, Vyga↗
NASA NTRS2019

Continuously Improving Parametric Modeling with Historical Data on the ICESat-2 Mission

This paper delves into the details of the Joint Confidence Level (JCL) process performed for the Ice, Cloud, and Land Elevation Satellite (ICESat)-2 mission and how past performance was incorporated into subsequent JCL models to enable the project to continuously analyze potential slips to their launch readiness date (LRD). One year prior to the mission Preliminary Review (mPDR), the JCL model development process began. The first model was well received at the mPDR, held on October 10, 2012, and the input received by the Standing Review Board was incorporated into the model for the official data drop for key decision point (KDP)-C. The 70% JCL results of the October 2012 mPDR model forecast an LRD of February 2017 and associated cost of $830M. This result in 2012 immediately highlighted potential challenges with the project-planned LRD of July 2016. The year following the mPDR, the project had sustained a oneyear slip in the LRD due to problematic systems engineering requirement issues which impacted all project subsystems. This slip moved the project planned LRD from July 2016 to July 2017, an additional 5 months beyond the 2012 model’s 70% JCL result for the LRD of February 2017. As the project was quickly approaching the mission Critical Design Review (mCDR), the need for reliable JCL results increased significantly. The project held discussions on the JCL modeling process and focused on the input uncertainty distributions. Specifically, to identify the uncertainty distributions that the 2012 mPDR model would have needed to produce a 70% LRD result of July 2017. This led the project to compare multiple uncertainty distributions, and ultimately spurred the project to utilize uncertainty distributions that incorporated project past performance and historical data to forecast potential LRD slips. The revised results, created in 2014 and utilizing the new uncertainty distributions, showed that with 70% confidence, the ICESat-2 mission would launch in August 2018 with a cost of $1,044M. Today, ICESat-2 is scheduled to launch on September 15, 2018 with a project management (PM) agreement value of $1,056M. This illustrates how a JCL model can be continuously improved to produce valuable results for a project, even in cases of LRD delays. The primary reason for the ICESat-2 LRD delay is due to a laser failure on the primary instrument. Laser failure was one of the highest risk and uncertainty drivers within the JCL model. The project placed the most risk in this area of the model, and the model further identified the laser as the top risk driver and contributor to the LRD result. This further illustrates how a JCL can be used to predict and quantify possible issues on new technology missions.

Krygiel, Joseph↗
NASA NTRS1981

PAN AIR: A computer program for predicting subsonic or supersonic linear potential flows about arbitrary configurations using a higher order panel method. Volume 4: Maintenance document (version 1.1)

The Maintenance Document is a guide to the PAN AIR software system, a system which computes the subsonic or supersonic linear potential flow about a body of nearly arbitrary shape, using a higher order panel method. The document describes the over-all system and each program module of the system. Sufficient detail is given for program maintenance, updating and modification. It is assumed that the reader is familiar with programming and CDC (Control Data Corporation) computer systems. The PAN AIR system was written in FORTRAN 4 language except for a few COMPASS language subroutines which exist in the PAN AIR library. Structured programming techniques were used to provide code documentation and maintainability. The operating systems accommodated are NOS 1.2, NOS/BE and SCOPE 2.1.3 on the CDC 6600, 7600 and Cyber 175 computing systems. The system is comprised of a data management system, a program library, an execution control module and nine separate FORTRAN technical modules. Each module calculates part of the posed PAN AIR problem. The data base manager is used to communicate between modules and within modules. The technical modules must be run in a prescribed fashion for each PAN AIR problem. In order to ease the problem of supplying the many JCL cards required to execute the modules, a separate module called MEC (Module Execution Control) was created to automatically supply most of the JCL cards. In addition to the MEC generated JCL, there is an additional set of user supplied JCL cards to initiate the JCL sequence stored on the system.

Baruah, P. K.↗
NASA NTRS1989

User's guide: Programs for processing altimeter data over inland seas

The programs described were developed to process GEODYN-formatted satellite altimeter data, and to apply the processed results to predict geoid undulations and gravity anomalies of inland sea areas. These programs are written in standard FORTRAN 77 and are designed to run on the NSESCC IBM 3081(MVS) computer. Because of the experimental nature of these programs they are tailored to the geographical area analyzed. The attached program listings are customized for processing the altimeter data over the Black Sea. Users interested in the Caspian Sea data are expected to modify each program, although the required modifications are generally minor. Program control parameters are defined in the programs via PARAMETER statements and/or DATA statements. Other auxiliary parameters, such as labels, are hard-wired into the programs. Large data files are read in or written out through different input or output units. The program listings of these programs are accompanied by sample IBM job control language (JCL) images. Familiarity with IBM JCL and the TEMPLATE graphic package is assumed.

Au, A. Y.↗
NASA NTRS1990

PAN AIR: A computer program for predicting subsonic or supersonic linear potential flows about arbitrary configurations using a higher order panel method. Volume 4: Maintenance document (version 3.0)

The Maintenance Document Version 3.0 is a guide to the PAN AIR software system, a system which computes the subsonic or supersonic linear potential flow about a body of nearly arbitrary shape, using a higher order panel method. The document describes the overall system and each program module of the system. Sufficient detail is given for program maintenance, updating, and modification. It is assumed that the reader is familiar with programming and CRAY computer systems. The PAN AIR system was written in FORTRAN 4 language except for a few CAL language subroutines which exist in the PAN AIR library. Structured programming techniques were used to provide code documentation and maintainability. The operating systems accommodated are COS 1.11, COS 1.12, COS 1.13, and COS 1.14 on the CRAY 1S, 1M, and X-MP computing systems. The system is comprised of a data base management system, a program library, an execution control module, and nine separate FORTRAN technical modules. Each module calculates part of the posed PAN AIR problem. The data base manager is used to communicate between modules and within modules. The technical modules must be run in a prescribed fashion for each PAN AIR problem. In order to ease the problem of supplying the many JCL cards required to execute the modules, a set of CRAY procedures (PAPROCS) was created to automatically supply most of the JCL cards. Most of this document has not changed for Version 3.0. It now, however, strictly applies only to PAN AIR version 3.0. The major changes are: (1) additional sections covering the new FDP module (which calculates streamlines and offbody points); (2) a complete rewrite of the section on the MAG module; and (3) strict applicability to CRAY computing systems.

Purdon, David J.↗
NASA NTRS2023

NASA Standing Review Board Handbook

This handbook provides guidance based on best practices for the planning, preparation, review, reporting, and closeout of Standing Review Board (SRB) activities. Revision C updates the Revision B version of the SRB Handbook published in 2016 to incorporate updates to NASA Procedural Requirements (NPR) 7120.5F, NASA Space Flight Program and Project Management Requirements. These updates include: - Changing the Dissenting Opinion process to the Formal Dissent process, which retains the current process augmented with an expedited escalation path. - Updates to requirements for establishing an Agency Baseline Commitment (ABC) and for performing Joint Cost and Schedule Confidence Level (JCL) analyses for tightly coupled programs. - Additional requirements for performing a JCL analysis for single-project programs and projects over $1B Life-Cycle Cost (LCC). - Use of initial capability cost estimates instead of LCC estimates in specific, identified instances for single-project programs and projects that plan continuing operations and production, including integration of capability upgrades, with an unspecified Phase E end point. These single-project programs and projects define an initial capability during Phase A and develop an initial capability cost that establishes the ABC at Key Decision Point (KDP) C. Initial capability is the first operational mission flight (or as defined in the KDP B Review Plan) and is documented in the KDP B Decision Memorandum. Initial capability cost includes operations cost for the initial capability. The Phase E cost estimate for continuing operations and production is established separately as part of the Operational Readiness Review (ORR) and KDP E for the 5 years after initial capability and subsequently updated and documented annually for the next 5-year period. Upgrades during Phase E that meet the Agency criteria for a major project for external reporting are treated as projects for the purposes of establishing their own development ABC outside the Phase E cost estimate. The Phase E cost estimate is updated to include production and operations costs associated with these upgrades. Development, production, and operations costs of other (i.e., non-major) upgrades are included in the Phase E cost estimate. (See NPR 7120.5, Sections 2.4.1.5 and 2.4.1.6 and the NASA Space Flight Program and Project Management Handbook (PM Handbook), Section 5.5.4 for additional information.) The scope of the SRB’s assessment with respect to initial capability, Phase E cost estimate, and major upgrades for these single-project programs and projects is defined in the Terms of Reference (ToR).

Kevin Michael Gilligan↗
NASA NTRS2011

NASA Instrument Cost/Schedule Model

NASA's Office of Independent Program and Cost Evaluation (IPCE) has established a number of initiatives to improve its cost and schedule estimating capabilities. 12One of these initiatives has resulted in the JPL developed NASA Instrument Cost Model. NICM is a cost and schedule estimator that contains: A system level cost estimation tool; a subsystem level cost estimation tool; a database of cost and technical parameters of over 140 previously flown remote sensing and in-situ instruments; a schedule estimator; a set of rules to estimate cost and schedule by life cycle phases (B/C/D); and a novel tool for developing joint probability distributions for cost and schedule risk (Joint Confidence Level (JCL)). This paper describes the development and use of NICM, including the data normalization processes, data mining methods (cluster analysis, principal components analysis, regression analysis and bootstrap cross validation), the estimating equations themselves and a demonstration of the NICM tool suite.

JCL↗
NASA NTRS1976

Flexstab on the IBM 360

FLEXSTAB, an array of computer programs developed on CDC equipment, has been converted to operate on the IBM 360 computation system. Instructions for installing, validating, and operating FLEXSTAB on the IBM 360 are included. Hardware requirements are itemized and supplemental materials describe JCL sequences, the CDC to IBM conversion, the input output subprograms, and the interprogram data flow.

Pyle, R. S.↗
NASA NTRS1977

Study of the NASTRAN input/output systems

The basic characteristics of the NASTRAN level 16 I/O subsystem are presented with particular reference to blocking/deblocking aspects, I/O methods used on the IBM, CDC, and UNIVAC machines, definition of basic NASTRAN I/O control tables, and portability of parts of the I/O subsystem to other programs outside the NASTRAN environment are included. An explanation of the IBM primary, secondary, and tertiary files defined by the data definition (DD) cards in the NASTRAN JCL procedure. The explanation is intended to enlighten users as to the purpose of these DD cards, how they relate to one another, and why there are no similar type definition cards required on the CDC and UNIVAC versions. Enhancements designed to increase overall efficiency and decrease core requirements are also recommended.

Brown, W. K.↗
NASA NTRS1980

Image-based information, communication, and retrieval

IBIS/VICAR system combines video image processing and information management. Flexible programs require user to supply only parameters specific to particular application. Special-purpose input/output routines transfer image data with reduced memory requirements. New application programs are easily incorporated. Program is written in FORTRAN IV, Assembler, and OS JCL for batch execution and has been implemented on IBM 360.

Bryant, N. A.↗
NASA NTRS1986

Combining Structural and Substructural Mathematical Models

Automation reduces input length and potential data-entry errors. Matrix Automated Reduction and Coupling (MARC) program used for combining NASTRAN substructural models with primary structural model MARC also constructs job-control language (JCL) stream for NASTRAN batch job that utilizes previously-written user library of dynamic models. Minimizes lengthy input and reduces potential data-entry errors. MARC procedure used in assembling Space Shuttle orbiter dynamic models since 1983 and reduced NASTRAN modeling input time by as much as 50 percent. MARC program written in FORTRAN IV for interactive execution.

Choa, V. K.↗
NASA NTRS1990

NASTRAN migration to UNIX

COSMIC/NASTRAN, as it is supported and maintained by COSMIC, runs on four main-frame computers - CDC, VAX, IBM and UNIVAC. COSMIC/NASTRAN on other computers, such as CRAY, AMDAHL, PRIME, CONVEX, etc., is available commercially from a number of third party organizations. All these computers, with their own one-of-a-kind operating systems, make NASTRAN machine dependent. The job control language (JCL), the file management, and the program execution procedure of these computers are vastly different, although 95 percent of NASTRAN source code was written in standard ANSI FORTRAN 77. The advantage of the UNIX operating system is that it has no machine boundary. UNIX is becoming widely used in many workstations, mini's, super-PC's, and even some main-frame computers. NASTRAN for the UNIX operating system is definitely the way to go in the future, and makes NASTRAN available to a host of computers, big and small. Since 1985, many NASTRAN improvements and enhancements were made to conform to the ANSI FORTRAN 77 standards. A major UNIX migration effort was incorporated into COSMIC NASTRAN 1990 release. As a pioneer work for the UNIX environment, a version of COSMIC 89 NASTRAN was officially released in October 1989 for DEC ULTRIX VAXstation 3100 (with VMS extensions). A COSMIC 90 NASTRAN version for DEC ULTRIX DECstation 3100 (with RISC) is planned for April 1990 release. Both workstations are UNIX based computers. The COSMIC 90 NASTRAN will be made available on a TK50 tape for the DEC ULTRIX workstations. Previously in 1988, an 88 NASTRAN version was tested successfully on a SiliconGraphics workstation.

Chan, Gordon C.↗
NASA NTRS2011

Juggling Act: Re-Planning and Building on Observatory...Simultaneously!

SOFIA (Stratospheric Observatory for Infrared Astronomy) is a major SMD program that has been required to meet several requirements and implement major planning and business initiatives overthe past 1 1/2 years, in the midst of system development and flight test phases. The program was required to implementing JCL and EVM simultaneously, as well as undergo a major replan and Standing Review Board - and all without impacting technical schedule progress. The team developed innovative processes that met all the requirements, and improved Program Management process toolsets. The SOFIA team, being subject to all the typical budget constraints, found ways to leverage existing roles in new ways to meet the requirements without creating unmanageable overhead. The team developed strategies and value added processes - such as improved risk identification, structured reserves management, cost/risk integration - so that the effort expended resulted in a positive return to the program.

Zavala, Eddie↗
NASA NTRS2014

Latest NASA Instrument Cost Model (NICM): Version VI

The NASA Instrument Cost Model, NICM, is a suite of tools which allow for probabilistic cost estimation of NASA's space-flight instruments at both the system and subsystem level. NICM also includes the ability to perform cost by analogy as well as joint confidence level (JCL) analysis. The latest version of NICM, Version VI, was released in Spring 2014. This paper will focus on the new features released with NICM VI, which include: 1) The NICM-E cost estimating relationship, which is applicable for instruments flying on Explorer-like class missions; 2) The new cluster analysis ability which, alongside the results of the parametric cost estimation for the user's instrument, also provides a visualization of the user's instrument's similarity to previously flown instruments; and 3) includes new cost estimating relationships for in-situ instruments.

Mrozinski, Joe↗