Staging from Development

On the Stage Options menu, choose Option 1 Dev to stage a component that resides in a library other than your package staging libraries. The component you stage from development is first copied into a package staging library. Then, if the component is like- source, build processing is initiated.

Three administration entries can restrict your use of stage from development:

Checkout Enforcement can require you to use checkout to get a component into your package if it already exists in an application baseline library.
Staging Restriction can prevent you from staging a component that does not already reside in your application baseline.
Overlay Prior Staged Module can prevent you from overlaying an existing package component that was last staged by someone else.

Ask your administrator if checkout is enforced and if you are permitted to create new components in ChangeMan ZMF.

You can use stage from development to process multiple components in a mass stage, but all components in a mass stage must be staged in the same library type.

On the Stage Options menu, choose Option 1 Dev and press Enter. The Stage: From Development (CMNSTG02) panel is displayed.

CMNSTG02                    Stage from Development
Command ===>_____________________________________________________
        Package: GENL000008         Status: DEV             Install date: 20180228

ISPF Library:
    Project . . . . __________
    Group . . . . . ______________________________
    Type . . . . .  __________
    Member . . . .  __________      (Blank/pattern for list; * for all members)

Other partitioned, sequential or zFS dataset:
    DSN . . . . . . ______________________________________________ +
Org . . . . . .     _______         (PDS, Seq, PAN, LIB, Oth, zFS)

Library type . . . . . ______       (Blank for list)
Stage name . . . . . . ____________________________________________+
Stage mode . . . . . . 1            (1-Online, 2-Batch)

Enter "/" to select option
    / Confirm request           ___ Expand zFS subdirectories
    / Lock component            ___ Display component user options
__ Extract Stored Procedure from Db2 catalog

This table describes the fields on the Stage: From Development panel.

Field	Description
ISPF Library	Use this group of fields to type the name of an ISPF library containing the component to be staged. An ISPF library is a cataloged partitioned data set with a three-level data set name in this format: project.group.type The library name can also be entered in the fields under the heading Other Partitioned, Sequential, or zFS Dataset.
Project Group Type	Enter the three nodes of an ISPF Library name in these fields. Member - Type one of the following:
	Blank: Display a library member selection list after the Stage: From Development panel.
	Member name: Stage one library member.
	Pattern: Display a partial member selection list after the Stage: From Development panel. A member name pattern contains one or more characters followed by an * wildcard
	*: Mass stage all members in the library.
	Caution: If you enter * in the Member field, every member in the library will be staged into your change package.
Other, partitioned, sequential or zFS dataset	Use this group of fields to enter the name of a partitioned or sequential data set or an zFS path that contains the component to be staged. An ISPF library name can be entered here or in the fields under the heading ISPF Library.
DSN	Enter the name of a partitioned data set, PDSE, sequential data set, or zFS directory or path. Quotes work the same as in your standard ISPF session. If the file is in zFS, the DSN must specify (end with) a directory, not a file name. If the file is a sequential data set, you must type a component name in the STAGE NAME below. If the file is a PDS, PDSE, a CA Panvalet library, or a CA Librarian master, type the member name in parentheses as follows:
	No member: Display a library member selection list after the Stage: From Development panel.
	Member name: Stage one library member.
	Pattern: Display a partial member selection list after the Stage: From Development panel. A member name pattern contains one or more characters followed by an * wildcard
	*: Mass stage all members in the library.
	Caution: If you type (*) for a member name, every member in the library will be staged into your change package.
Org	Enter the type of file from which you are staging:
	PDS: Partitioned dataset or PDSE
	SEQ: Sequential dataset
	PAN: CA Panvalet library
	LIB: CA Librarian master
	ZFS: z/OS File System
	Oth: Other, such as ROSCOE
	Blank: ChangeMan ZMF determines whether the file organization is PDS or SEQ by the presence of a member name and/or a STAGE NAME
Library type	Enter the library type under which you will stage the component. Leave this field blank to display the Library Type Selection List panel.
Stage name	Enter the name under which you want to stage the component, if: You are staging a component from a sequential file. You want to change the name of a member staged from a PDS, CA Panvalet, or CA Librarian library. This field is often cleared when an error message is displayed on the Stage: From Development panel. If you type information in Stage Name, and panel processing stops with an error message, you may need to reenter Stage Name.
Stage mode	See Online and Batch Execution Modes
	1. Stage in online mode.
	2. Stage in batch mode.
	Enter '1' to submit multiple members online, however, online execution may tie up your terminal with JES messages.
	Enter '2' to allow staging of several components in background from a single job submission.
Expand	If you specify zFS in the ORG field, a component selection panel is displayed after the Stage: From Development panel. The Expand field determines what is displayed on that selection list.
	Select to list files in the last directory path you entered in the DSN field. Also, list subdirectories and paths in the last directory in the DSN path. If not selected it will not list subdirectories or paths in the last directory in the DSN path.
Confirm request	Activate confirmation panels for checkout, stage, and component delete that permit you to cancel a function after you have initiated the process but before it is executed. There are two confirmation panels for Stage From Development: Display a list of other packages that contain the component being staged. Display a warning if the stage process will overlay a component already resident in the staging library. N Suppress confirmation panels in checkout, stage, and component delete.
Lock component	Select to lock component being staged from development. See Locking and Unlocking Package Components Omit to stage the component without locking it. This only applies to the current package. Omit to bypass locking the component. If the component is already locked in the package, it will remain locked.
Display component user options	Allow display of component user option panel(s) for non-source components. This allows user data to be associated with a component for later use in exits or XML services. Only applies to the current package. Omit to bypass locking the component. If the component is already locked in the package, it remains locked.
Extract Stored Procedure from Db2 catalog	Connect to Db2 (v11 and later) and extract a native SQL Stored Procedure definition directly into a ZMF package component.

Type the information you want on the Stage: From Development panel and press Enter.

When you stage from development, you are allowed to copy a component into your package that already resides in your staging library. However, before the copy is executed, an Overlay Warning (CMNSTGWP) panel is displayed.

+----------------------- Stage Warning ----------------------+
| CMNSTGWP                                                   |
| Command ===> ______________________________________________|
|                                                            |
| Staging Member:                                            |
|   GNLSRC1A                                                 |
| Will overlay USER106 version.                              |
|                                                            |
+------------------------------------------------------------+

If you want to overlay the component in your staging library, press Enter. Otherwise, press PF3 or type End in the Command line. Press Enter to stop the stage from development process.

When a component is copied to a staging library by stage from development, ISPF statistics in the staging library directory are set as follows.

ISPF Stat	Staged From Sequential File	Staged From PDS(E)
VV.MM	Set to 01.01	Set to 01.01
CREATED	Set to the stage date	Copied from the directory of the originating library
CHANGED	Set to the stage date/time	Set to the stage date/time
SIZE	Set to the number of records in the file	Copied from the directory of the originating library
INIT	Set to the number of records in the file	Copied from the directory of the originating library
ID	Set to the TSO ID of the person who staged the component	Set to the TSO ID of the person who staged the component

If you stage from a sequential file, or if you specify a member name on the Stage: From Development (CMNSTG03) panel, only one component is staged, and the rest of the stage from development process is like a stage from package. For a description of the rest of the stage process.
If you stage from a PDS(E) and you specify * for the member name, mass stage is invoked. Go to Mass Stage.

If you stage from a PDS(E) but do not specify a member on the Stage: From Development (CMNSTG03) panel, or if you specify a name pattern for a member name, the Stage: From - library is displayed to give you a list of components.

CMNSTG03            Stage from Development      Row 1 to 2 of 2
Command ===>__________________________________ Scroll ===> CSR

From dataset name
USER016.USER.SRCLIB

Name    Function vv.mm Created          Changed          Size  Init  User
GNLSRC1A         01.01 2002/05/07       2015/01/05 01:22 00028 00022 USER016
GNLSRC99         01.01 2002/05/07       2015/01/05 00:54 00022 00015 USER016
******************************* Bottom of data ********************************

This table describes the fields on the Stage From - library panel.

Field	Description
COMMAND	Enter one of the following commands, or leave the command line blank and type a line command next to a component name.
	BROWSE member: Browse the specified member in the development library. Abbreviation: B
	HISTORY member: List component history for the specified member. Abbreviation: H
	STAGE: Mass Stage members selected on this panel. See Mass Stage
	STAGE ALL: Mass Stage all members on the component list. Selection is not required. See Mass Stage
	REFRESH: Display updated information on this panel. Abbreviation: R
	SORT heading: Sort listed components by information under the specified column heading.
	LOCATE member: Locate a listed component by information in the last sorted column or by Name if the components were not sorted. Abbreviation: L
	CANCEL: Cancel selections and exit this panel. Abbreviation: C.
Line Command	Enter a line command to the left of the Name row. If the Stage From - library panel extends over multiple screens, line commands on the current screen are processed before the next screen is displayed.
	B: Browse the member in the development library.
	H: List component history for the member
	S: Select a member for stage
	M: Select for mass stage. This line command is equivalent to using the S line command plus the Stage command at the top of the panel.
	V: View a component in edit like mode
	If S and M line commands are entered on the same panel, all selections are treated as M and are mass staged.

If you select one or more components on the Stage From - library panel that are not SRC or like-source:
- Selected components are copied to the staging library.
- The component status for staged components is set to Active.
- The Function field on the Stage From - library panel is set to *Stage.
Stage from development is complete. Press PF3 or type End in the Command line. Press Enter to return to the Stage: From Development panel.
If you select SRC and like-source components on the Stage From - library panel, the next steps depend on how you select those components:
- If you type S in the line command for one or more components, and if you do not type STAGE in the Command line, each selected member is staged as an individual component. Go to Step 6 in Staging from Package for a description of the steps each component must pass through to complete the stage process.
- All other selection methods on the Stage: From library panel invoke mass stage.

Mass Stage

Mass stage:

- Stages multiple components under the same library type.
- Submits a separate stage job for each component.
- Can force all components to be staged using the same procedure and parameters, or it can use procedures and parameters found in component history and in **Designated Procedures**.
- Uses the same staging versions **Component Change Description** for all staged components.

You invoke mass stage when you do any of the following for components in stage from development:
- Enter **\*** for the member name on the **Stage: From Development** (CMNSTG02) panel.
- Select members on the **Stage: From library** (CMNSTG03) panel with **M** in the **line command**.
- Select members on the **Stage: From library** (CMNSTG03) panel with **S** in the **line command** and enter **STAGE** in the **Command** line.
- Enter **STAGE ALL** in the **Command** line of the **Stage: From library** (CMNSTG03) panel.

In this example, the library outside of ChangeMan ZMF where components reside is coded in the Partitioned, Sequential, Panvalet, Librarian, Other or zFS Dataset field, and the Library Type field is set.

CMNSTG02                Stage from Development
Command ===> __________________________________________
    Package: GENL000008     Status: DEV     Install date: 20150228

ISPF Library:
Project . . . . ___________
Group . . . . . __________________________
Type . . . . .  ___________
Member . . . .  ___________     (Blank/pattern for list; * for all members)

Other partitioned, sequential or zFS dataset:
DSN . . . . . . USER016.USER.SRCLIB                                       +
Org . . . . . . ______          (PDS, Seq, PAN, LIB, Oth, zFS)
Library type . . . . . SRC      (Blank for list)
Stage name . . . . . . __________________________________________________ +
Stage mode . . . . . . 1        (1-Online, 2-Batch)

Enter "/" to select option
/ Confirm request       __Expand zFS subdirectories
/ Lock component        __Display component user options
__Extract Stored Procedure from Db2 catalog

Press Enter to display the Stage From - library (CMNSTG03) panel.

CMNSTG03            Stage from Development                  Row 1 to 2 of 2
Command ===> _____________________________________________ Scroll ===> CSR

From dataset name
USER016.USER.SRCLIB

  Name     Function vv.mm Created    Changed          Size  Init  User
M GNLSRC1A CANCEL   01.01 2002/05/07 2015/01/05 01:22 00028 00022 USER016
M GNLSRC99 CANCEL   01.01 2002/05/07 2015/01/05 00:54 00022 00015 USER016
******************************* Bottom of data ******************************

On the Stage From - library (CMNSTG03) panel, select components for mass stage. In this case, M is entered in the Line Command for components to be staged. Then press Enter to display the Stage: Mass Build (CMNSTG05) panel where you set the build process procedure and options.

CMNSTG05                Stage: Mass Build
Command ===>___________________________________________

    Package: GENL000006     Status: DEV         Install date: 20150228
Library type . . . . SRC - Source for Programs to be Linked Executable
Dataset name . . .   USER016.USER.SRCLIB
Language . . . . . . . . . _________ (Blank for list)
Compile procedure . . . .  _________ (Blank for list)
Compile parms . . . . . .  _________
Pgm binder parms . . . . . ____________________________________
Enter "/" to select option ____________________________________
    Db2 precompile
    Precompile variables
/ Other options
__ Suppress history
__ Suppress messages
/  Increment jobname
Job statement information:
    //USER016 JOB (0000),'CHANGE MAN',
    //            CLASS=A, NOTIFY=USER016,MSGCLASS=X
//*
//*

This table describes the fields on the Stage: Mass Build panel.

Field	Description
Package	Displays the current package ID.
Status	Displays the current status of the change package.
Install date	Displays the date when this package is proposed for installation. (yyyymmdd).
Library type	Displays the SRC or like-source library type specified on the Stage: From Development panel.
Dataset name	Displays the name of the file specified on the Stage: From Development panel.
NOTE:
	There is no component history for a component, or
	The Suppress History field below is selected and there is no Designated Procedure with Force Level 2 for a component.
Language	Enter the source language. If the Language field is blank, the Language Selection List is displayed when you press Enter.
Compile procedure	Identify the compile procedure to be used to stage the component. Compile procedures are members in the ChangeMan ZMF skeleton library that are processed by ISPF file tailoring to create stage JCL. If the Compile Procedure field is blank, and if there are multiple Compile Procedures defined in administration for the specified Language, the Compile Procedure Selection List panel is displayed when you press Enter. If the Compile Procedure is blank, but there is only one Compile Procedure defined for the specified Language, the Compile Procedure is filled automatically when you press Enter.
Compile parms	Enter compile options that are not already in effect through: System defaults. Compile Procedure skeletons. User Options. See Other Options below.
Pgm binder parms	Enter pgm binder parms that are not already in effect through: System defaults for the compiler. Compile Procedure skeletons. User Options. See Other Options below.
Db2 precompile	Select to include a Db2 precompile step in the stage job.
	Omit to bypass Db2 precompile step in the stage job.
Precompile variables	Select to display the Db2 Physical Subsystems panel to set additional options for Db2 components. Field Db2 Precompile must be selected.
	Omit to bypass display of Db2 Physical Subsystems panel.
Other options	Select to display the Stage: User Options panel before submitting the stage job.
	Omit to bypass display of Stage: User Options panel before submitting the stage job.
Suppress history	Select to suppress component history and use the procedure and parameters on this panel (and on the Stage: User Options panel, if displayed) to stage all components except those with a Designated Procedure that has a Force Level 2.
	Obtain stage procedure and parameters for each component in this order:
	1. Designated Procedure with Force Level 2.
	2. Component history.
	3. Entries on this panel (and on the Stage: User Options panel, if displayed).
**NOTE:
Suppress message	Suppress the SEND message normally broadcast at the completion of each stage job that tells you whether the component was staged successfully. (The job submitted message for the stage job is also suppressed.)
	Broadcast a SEND message at the completion of each stage job to tell you whether the component was staged successfully.
Increment jobname	Determines whether job name suffixes for staging jobs submitted by mass state are incriminated to allow multiple jobs to run at the same time. The job name in the Job Statement Information field must consist of the submitter’s TSO userid followed by a one character alpha suffix, A-Z. Job name suffixes 0-9, @, #, and $ are not incriminated. There is no relationship between this option and JOB NAME INCREMENT OVERRIDE in ZMF administration.
	Increment job name suffix, allowing multiple jobs to run simultaneously.
	Do not increment the job name suffix. Force jobs to single thread.
Job statement information	Enter valid job card information for your site.

When you finish entries on the Stage: Mass Build panel, press Enter.

Stage job JCL for each mass staged component is created in a separate file tailoring started task and submitted through the internal reader.