The VMSES/E VMFBLD exec calls ARISAVES to load and save each segment.
>>-ARISAVES----COMPONENT(compid)---ORIGIN(origin)---------------> >-----SYSNAME(name)---+--------------+------------------------->< '-STORKEY(key)-' |
Specify the origin that your System Programmer determined for the saved segment.
Specify the name you specified for the saved segment name in the OBJNAME field of the Add Segment Definition panel. See Chapter 8, Saved Segments. For example, SQLSQLDS for the DBSS component.
If you omit this parameter, 13 is used for STORKEY. Normally, you would not specify this parameter.
+---------------------------VMSES/E Consideration----------------------------+
To use a different storage key, you need to change the build lists for the
segments you are going to use. The following table lists the segment
and their corresponding build list name.
Segment Name | Buildlist Name |
---|---|
SQLRMGR | ARIBLMGR |
SQLISQL | ARIBLISQ |
SQLSQLDS | ARIBLDBS |
SQLXRDS | ARIBLRDS |
LANGS001 | ARIBLLNG |
To change the build lists, you must use the VMSES/E local modification procedures described in the "Local Modifications for DB2 for VM" appendix in the DB2 Server for VM Program Directory.
+------------------------End of VMSES/E Consideration------------------------+
For example, to save the DBSS at origin B00000, invoke the ARISAVES EXEC as follows:
ARISAVES COMPONENT (DBSS) ORIGIN (B00000) SYSNAME (SQLSQLDS) |
The ARISAVES EXEC does the following:
The ARISSEGC MACRO identifies the contents of the default (SQLDBA) bootstrap package. For more information, see Step 12. Update the ARISSEGC Macro.
If you reply NO, you must create a bootstrap package yourself by using the SQLGENLD EXEC shown in Step 15. Create a Bootstrap Package.