)CM
)CM                                                                             
)CM ================================================================ */         
)CM PROPRIETARY-STATEMENT:                                           */         
)CM Licensed Material - Property of IBM                              */         
)CM                                                                  */         
)CM 5724-I63, 5724-H88, 5655-N01, 5733-W61                           */         
)CM (C) Copyright IBM Corp. 1999, 2007                               */
)CM All Rights Reserved                                              */         
)CM US Government Users Restricted Rights - Use, duplication or      */         
)CM disclosure restricted by GSA ADP Schedule Contract with IBM Corp.*/         
)CM ================================================================ */         
)CM                                                                  */         
)CM Change Activity:                                                 */         
)CM                                                                  */         
)CM   xxxxxxxxx H28W600 100704  PDML: Initial release.               */         
)CM   245851    H28W600 113004  PDML: update instructions.           */         
)CM   246267    H28W600 120304  PDML: small update to instructions.  */         
)CM   246983    H28W600 121604    DB: Revise instructions based on   */         
)CM                                   new dataset panels             */         
)CM   249091    H28W601 011005  DB: Updates based on review comments */         
)CM   250869    H28W601 012005    DB: Second review update           */         
)CM   252044    H28W601 012705    DB: Fix some typos                 */         
)CM   255937    H28W601 021705  PDML: update instruction.            */         
)CM   257033    H28W601 022205    DB: update for additional RACF     */         
)CM                                   support                        */         
)CM   257602    H28W601 022405    DB: revise instructions            */         
)CM   256827    H28W601 022405  DB:   add additional RACF            */         
)CM                                   instructions                   */         
)CM   256827.1  H28W601 030205  PDML: update RACF syntax.            */         
)CM   259928  H28W602 041405    DB: Only  generate BBORTSS5 section  */         
)CM                                 if answer for in STEPLIB is Y    */         
)CM   253275    H28W602 041505  DB: remove reference to BBOWTR       */         
)CM                                 and ATTRRS                       */         
)CM   290470    H28W602 071805 PDML: remove GSK.                     */         
)CM   311865    H28W610 100805  DB: remove SCEERUN items             */         
)CM LIDB3709-34 H28W610 101105  PDML: update migration instructions. */         
)CM   321816    H28W610 111005  PDML: update migration instructions. */         
)CM   325782    H28W610 112205   DB: change BBORTSS5 to BBORTS61     */         
)CM   331632    H28W610 121305   DB: use MBBOLPA instead of BBOLPA   */         
)CM   330776  H28W610 121405    DB: update instructions based on     */         
)CM                                 change to SBBOLPA/SBBOLOAD       */         
)CM   337853    H28W610 011206   DB:  fix some typos                 */         
)CM   333384    H28W610 011406   DB: add zfs support                 */         
)CM  333384.1 H28W610 011906    DB: filesystem should be two words   */         
)CM  337515   H28W610 012306    DB: updates for STEPLIB changes      */         
)CM   330804   H28W610 013006   DB: add automount warning            */         
)CM  342400   H28W610 013006    DB: change FILEZFS to FSTYPE         */         
)CM  338132   H28W610 020606  PDML: add SBBGLOAD.                    */         
)CM  356728   H28W610 040306    DB: use ASFSTYPE                     */         
)CM  364931   H28W610 042406    DB: updates for non root install     */         
)CM  365720   H28W610 042706    DB: updates for required SAF profiles*/         
)CM  368261   H28W610 051106    DB: updates for mount point          */         
)CM 365720.1  H28W610 051206    DB: more SAF updates                 */         
)CM  363993   H28W610 062206    LA: more updates for SAF PFSCTL      */         
)CM  347707   H28W610 062306    DB: update text for a userid         */         
)CM  367238   H28W610 062906    DB: move BBOMMCP in instructions     */         
)CM  373993   H28W610 082206    DB: SAF profile update for zFS       */         
)CM  370154   H28W610 083106    DB: add verify stmt for HFS job      */         
)CM  400982   H28W610 102606    DB: Add text for AUTOMOVE            */         
)CM  402402   H28W610 110106    DB: Reword AUTOMOVE text             */         
)CM  412596   H28W610 010307    DB: Add SBBGLOAD references          */         
)CM  412597   H28W610 010807    DB: fix minor text issues            */
)CM  PK39840  H28W700 022207    RG: edit migration instructions      */
)CM  422082   V7.0    060707  PDOP: Truncated lines exceeding 72 char*/
)CM  488021   V7.0    121007   CDH: Updated for 7.0                  */
)CM  530741   2008620 guorong  remove 'Z' procs                      */
)CM  PM14512  2010520 rvscott  Update inst to include both Migr opts */
)CM  657201   2010623 kkaggarw Correction of 7.0 references          */
)CM  698264.1 2011407 vijaylax Document local_policy.jar migration   */
)CM ================================================================ */
                                                                                
)BLANK
)BLANK                                                                          
------------------------------------------------------------------
Instructions for migrating a WebSphere Application Server for z/OS
federated application server node

)BLANK
If your back-level version of WebSphere Application Server is using 
the unrestricted jurisdiction policy files, you must perform the 
following special step to migrate these files to your new version of 
WebSphere Application Server. If you are not using the unrestricted 
jurisdiction policy files, you do not need to take the following step.

)BLANK
Before migrating, copy the modified local_policy.jar file to a 
temporary location.
                                                                                
)BLANK
The z/OS Migration Management Tool has created jobs based on the
information that you provided. These instructions tell you how to
modify the operating system and run the jobs to migrate WebSphere
Application Server for z/OS.
                                                                                
)BLANK
Guidelines:

)BLANK
    - If you created the target data sets (*.CNTL and *.DATA) on
      another (driving) system, you must copy them to the target
      system and give them the same data set names.

)BLANK
    - You must use these instructions on your target system.

)BLANK
Performing manual configuration updates
---------------------------------------
                                                                                
)BLANK
The z/OS Migration Management Tool for WebSphere Application Server
for z/OS does not attempt to update configuration data for your base
operating system or existing subsystems. You must take the following
manual steps before running the WebSphere Application Server for z/OS
migration jobs. Because you are migrating an existing system, some of
these steps might have already been taken during your previous
installation.

)BLANK
    -------------------------------------------------------------------
                                                                                
)BLANK
1.  Update your active BPXPRMxx member to have the following WebSphere
    Application Server for z/OS configuration file system:

)BLANK
    &MMHFS.

)BLANK
    mounted at:

)BLANK
    &MMMOUNTP.

)BLANK
    in read and write mode.

)BLANK
    For example:

)BLANK
       MOUNT FILESYSTEM('&MMHFS.')
       MOUNTPOINT('&MMMOUNTP.')
       TYPE(&ASFSTYPE.)
       MODE(RDWR)

)BLANK
    If you are configuring in a sysplex environment, you might want to
    add the NOAUTOMOVE parameter as follows:

)BLANK
       MOUNT FILESYSTEM('&MMHFS.')
       MOUNTPOINT('&MMMOUNTP.')
       TYPE(&ASFSTYPE.)
       MODE(RDWR) SYSNAME(<system_name>) NOAUTOMOVE

)BLANK
    The NOAUTOMOVE parameter in this example prevents the
    configuration file system from being mounted on a different z/OS
    system in a shared file system configuration, which could cause
    performance problems.  Replace <system_name> with the applicable
    system name for your installation.

)BLANK
    -------------------------------------------------------------------

)BLANK                                                                          
2.  WebSphere Application Server for z/OS customization assumes that
    the following system data sets are in the system link list or link
    pack area:

)BLANK
    Language Environment     SCEERUN
                             SCEERUN2

)BLANK
    System SSL               SIEALNKE (z/OS 1.6 and above)

)BLANK
    Placing these data sets in the link list or link pack area improves
    performance and insulates your WebSphere Application Server for
    z/OS configuration from changes in data set names (for example,
    when migrating to z/OS 1.6).

)BLANK
    If the Language Environment or System SSL load module libraries are
    not in your system link list or link pack area, you must perform
    the following steps before starting any WebSphere Application
    Server for z/OS servers:

)BLANK
    - Make sure that the data sets are APF-authorized.

)BLANK
    - Complete the optional step below to add the data sets to STEPLIB
      in the server JCL and setupCmdLine.sh scripts.

)BLANK
    If you regenerate server cataloged procedures at any point, make
    sure that the data sets are added to the new cataloged procedures.

)BLANK
    -------------------------------------------------------------------

)BLANK                                                                          
3.  Set up security system rules to run the Version 8.5 daemon and
    federated node controllers under the same user IDs as used for              
    your previous version. (This assumes that the same Version 8.5 
    cataloged procedure is used for both the node agent and 
    application server controller's federated node.)

)BLANK
    If you use RACF for your security system, use the following                 
    instructions.  If you use another SAF-compliant security system,            
    contact the security system vendor for appropriate information. 

)BLANK                                                                          
    Check your MVS system log or use the TSO RLIST STARTED command to           
    determine the user ID and group under which your previous daemon            
    runs. (The previous default daemon user ID and group are WSDMNCR1
    and WSCFG1.)  Then, issue the following RACF command to create a
    corresponding STARTED profile for the Version 8.5 daemon cataloged
    procedure:

)BLANK                                                                          
        RDEFINE STARTED &MMDPN..*                                               
                STDATA(USER(user) GROUP(group) TRACE(YES))                      
        SETROPTS RACLIST(STARTED) GENERIC(STARTED) REFRESH

)BLANK                                                                          
    Check your MVS system log or use the TSO RLIST STARTED command
    to determine the user ID and group under which your previous
    node agent and application server controller run. Then, issue
    the following RACF command to create a corresponding STARTED
    profile for the Version 8.5 federated node controller cataloged
    procedure:

)BLANK                                                                          
        RDEFINE STARTED &MMCPN..*                                               
                STDATA(USER(user) GROUP(group) TRACE(YES))                      
        SETROPTS RACLIST(STARTED) GENERIC(STARTED) REFRESH

)BLANK                                                                          
    Because the STARTED profile for the application server servant              
    in the federated node is based only on the job name, no additional
    STARTED profile should be needed for the application server
    servant, which has the same job name before and after migration.

)BLANK                                                                          
    -------------------------------------------------------------------

)BLANK                                                                          
4.  Add the security profiles that were first required in Version 6.1.

)BLANK
    If you use RACF for your security system, use the following
    instructions.  If you use another SAF-compliant security system,
    contact the security system vendor for appropriate information.  

)BLANK                                                                          
    Check your MVS system log or use the administrative console to              
    determine if Enable Trusted Applications is set for your node.              
    (Look for control_region_security_enable_trusted_applications in            
    the startup log;  if it is set to 1, then Enable Trusted 
    Applications is set.)  If it is set, create the following SAF 
    profile and grant READ access to the application server control 
    region user ID for each server in the node.

)BLANK
        BBO.TRUSTEDAPPS.<cell_shortname>.<cluster_name>

)BLANK                                                                          
    If the server is not clustered, use the cluster transition name             
    (server generic short name) in place of <cluster_name>.

)BLANK                                                                          
    Use the following RACF commands to accomplish this:

)BLANK                                                                          
        RDEFINE FACILITY BBO.TRUSTEDAPPS.<cell_shortname>.**
                UACC(NONE)                                                      
        PERMIT  BBO.TRUSTEDAPPS.<cell_shortname>.**
                CLASS(FACILITY) ID(<config_group>) ACCESS(READ)
        SETROPTS RACLIST(FACILITY) REFRESH

)BLANK                                                                          
    Check your MVS system log or use the administrative console to              
    determine if Sync to OS Thread Allowed is set for your servers.             
    If it is set, create the following SAF profile and grant either
    READ or CONTROL access to the application server control region
    user ID for each server:

)BLANK                                                                          
        BBO.SYNC.<cell_shortname>.<cluster_name>

)BLANK                                                                          
    If the server is not clustered, use the cluster transition name             
    (server generic short name) in place of <cluster_name>.

)BLANK                                                                          
    Granting CONTROL access to the application server control region            
    user ID allows the thread identity to be switched to any user               
    ID that requests Sync to OS Thread:

)BLANK                                                                          
        RDEFINE FACILITY BBO.SYNC.<cell_shortname>.**
                UACC(NONE)                                                      
        PERMIT  BBO.SYNC.<cell_shortname>.**
                CLASS(FACILITY) ID(config_group) ACCESS(CONTROL)                
        SETROPTS RACLIST(FACILITY) REFRESH

)BLANK                                                                          
    As an alternative, you can grant the control region READ access             
    to this profile, which restricts the user IDs to which the thread           
    identity can be changed based on SAF SURROGAT profiles.  See
    the Version 8.5 information center for more information.

)BLANK                                                                          
    Note that Enable Trusted Applications must be set if the LocalOS            
    registry or SAF authorization is used.  If needed, the new
    SAF profiles must be created before servers are started at                  
    Version 8.5.
                                                                                
)BLANK
Running the migration jobs
--------------------------

)BLANK
The z/OS Migration Management Tool built a number of batch jobs with
the variables that you supplied. You must run the jobs in the order
listed below using user IDs with the appropriate authority.

)BLANK
Note: Whenever "file system update authority" is indicated, the user
      ID used to run the configuration job must have EITHER uid = 0
      OR the following UNIXPRIV class profile privileges:

)BLANK
        CONTROL access to SUPERUSER.FILESYS
        UPDATE  access to SUPERUSER.FILESYS.MOUNT
        READ    access to SUPERUSER.FILESYS.CHOWN
        READ    access to SUPERUSER.FILESYS.CHANGEPERMS
        READ    access to SUPERUSER.FILESYS.PFSCTL

)BLANK
      If the UNIXPRIV profile CHOWN.UNRESTRICTED is defined, then
      the SUPERUSER.FILESYS.CHOWN is not required.  For information
      about the UNIXPRIV class, see the z/OS Unix System Services
      Planning book.

)BLANK
Before you begin, complete the section above that is titled
"Performing manual configuration updates."

)BLANK
When running with multiple TCP/IP stacks, you must add the environment
variable _BPXK_SETIBMOPT_TRANSPORT to ensure the migration job uses
the proper TCP/IP stack. Modify the JCL for both BBOWMG3F and BBOWMPOS
to add the following line: 
      export _BPXK_SETIBMOPT_TRANSPORT=<stack.name>
where <stack.name> is replaced with the appropriate stack ID. For more
information and an example, see the following article in the information
center: "Migrating a z/OS federated node."

)BLANK
Follow the steps in the table below, which lists in order the jobs
that you must submit and the commands that you must enter. Special
handling notes are included in the table. All jobs are members of

)BLANK
&TRGCNTL.

)BLANK
Attention: After submitting each job, carefully check the output.
Errors might exist even when all return codes are zero.

)BLANK
Unless otherwise indicated, these jobs must be submitted by a user ID
that has authority to alter file permissions, change file ownership,
and change group membership of all files.  Please read the instructions
for each job carefully before submitting it.
                                                                                
)BLANK                                                                          
)SEL &ASFSTYPE = HFS                                                            
+-----------+----------------------------------------------------------+        
| BBOMMHFS  | User ID requirement:                                     |
+-----------+                                                          |
|           | The user ID that submits this job must have file         |
| Done:     | system update authority (see above) and the              |
|           | authority to allocate                                    |
|           |                                                          |
| By:       | &MMHFS.                                                  |
|           |                                                          |
|           | Before running this job, do the following:               |
|           |                                                          |
|           | Verify that the DD statement that defines the data set   |
|           | is valid for the storage rules defined on the target     |
|           | system.                                                  |
|           |                                                          |        
|           | Warning: If you intend to update the same configuration  |
|           | file system as the one that contains the newly migrated  |
|           | deployment manager and it is still mounted, you do not   |
|           | need to run this job.                                    |
|           |                                                          |
|           | If you are required to manually create the directory     |
|           | structure, this job performs the following tasks:        |
|           |                                                          |
|           | o   Creates a mount point directory                      |
|           |                                                          |
|           |     &MMMOUNTP.                                           |
|           |                                                          |        
|           | o   Allocates the configuration file system using        |        
|           |     the hierarchical file system (HFS)                   |
|           |                                                          |
|           |     &MMHFS.                                              |
|           |                                                          |
|           | o   Mounts the file system at the mount point            |
|           |                                                          |        
|           | Do not run this job if any of the following are true:    |
|           |                                                          |
|           | o   The configuration file system already exists and is  |
|           |     mounted at the desired mount point.                  |
|           |                                                          |
|           | o   The mount point directory is controlled by           |
|           |     automount.                                           |
|           |                                                          |
|           |     Either disable the automount rule for the            |
|           |     configuration mount point while running this         |
|           |     job, or perform the following steps manually:        |
|           |                                                          |
|           |      1. Allocate the configuration file system data set. |
|           |                                                          |
|           |      2. Issue the following shell command, which will    |
|           |         also cause automount to mount the file system:   |
|           |                                                          |
|           |         chmod 775 &MMMOUNTP.                             |
|           |                                                          |        
|           | Before you begin:                                        |
|           |                                                          |
|           | The BBOMMHFS job assumes that your root file system is   |
|           | mounted in read and write mode. If it is not, manually   |
|           | create the directory                                     |
|           |                                                          |
|           | &MMMOUNTP.                                               |        
|           |                                                          |
|           | For example:                                             |
|           |                                                          |
|           | If you plan to use /WebSphere/V8R5 as your directory,    |
|           | issue the following command from within the OMVS shell:  |
|           |                                                          |
|           | mkdir -p -m 775 /WebSphere/V8R5                          |
|           |                                                          |
|           | Attention:                                               |
|           |                                                          |        
|           | The migration procedure will set the file ownership and  |
|           | permissions to match your previous configuration.        |
|           | Verify that the mount point directory is owned by your   |
|           | WebSphere Application Server administrator and that the  |
|           | group is assigned to the Administrators group. If it is  |
|           | not, then determine the user ID and group ID values that |
|           | are designated as owners of the previous WebSphere       |
|           | Application Server configuration. Either the numeric ID  |
|           | values or the user name and group name can be used.      |
|           | Issue the following command within the OMVS shell,       |
|           | replacing <user> and <group> with the user and group     |
|           | determined previously. Also replace <mountpoint> with    |
|           |                                                          |
|           | &MBMOUNTP.                                               |
|           |                                                          |
|           | chown <user>:<group> <mountpoint>                        |
|           |                                                          |        
)ENDSEL                                                                         
)SEL &ASFSTYPE = ZFS                                                            
+-----------+----------------------------------------------------------+        
| BBOMMZFS  | User ID requirement:                                     |
+-----------+                                                          |
|           | The user ID that submits this job must have file         |
| Done:     | system update authority (see above) and the              |
|           | authority to allocate                                    |
|           |                                                          |
| By:       | &MMHFS.                                                  |
|           |                                                          |
|           | Before running this job, do the following:               |
|           |                                                          |
|           | Verify that the DD statement that defines the data set   |
|           | is valid for the storage rules defined on the target     |
|           | system.                                                  |
|           |                                                          |
|           | Warning: If you intend to update the same configuration  |
|           | file system as the one that contains the newly migrated  |
|           | deployment manager and it is still mounted, you do not   |
|           | need to run this job.                                    |
|           |                                                          |
|           | If you are required to manually create the directory     |
|           | structure, this job performs the following tasks:        |
|           |                                                          |
|           | o   Creates a mount point directory                      |
|           |                                                          |
|           |     &MMMOUNTP.                                           |
|           |                                                          |
|           | o   Allocates the configuration file system using the    |
|           |     z/OS Distributed File Service zSeries File System    |
|           |     (zFS)                                                |
|           |                                                          |
|           |     &MMHFS.                                              |
|           |                                                          |
|           | o   Mounts the file system at the mount point            |
|           |                                                          |
|           | Do not run this job if any of the following are true:    |
|           |                                                          |
|           | o   The configuration file system already exists and is  |
|           |     mounted at the desired mountpoint.                   |
|           |                                                          |
|           | o   The mount point directory is controlled by           |
|           |     automount.  Either disable the automount rule for    |
|           |     the configuration mount point while running this     |
|           |     job, or perform the following steps manually:        |
|           |                                                          |
|           |     1. Allocate the configuration file system data set.  |
|           |                                                          |
|           |     2. Issue the following shell command, which will     |
|           |        also cause automount to mount the file system     |
|           |                                                          |
|           |        chmod 775 &MMMOUNTP.                              |
|           |                                                          |
|           | Before you begin:                                        |
|           |                                                          |
|           | The BBOMMZFS job assumes that your root file system is   |
|           | mounted in read and write mode.  If the root file system |
|           | is not mounted in read and write mode, manually          |
|           | create the directory                                     |
|           |                                                          |
|           | &MMMOUNTP.                                               |
|           |                                                          |
|           | For example:                                             |
|           |                                                          |
|           | If you plan to use /WebSphere/V8R5 as your directory,    |
|           | issue the following command from within the OMVS shell:  |
|           |                                                          |
|           | mkdir -p -m 775 /WebSphere/V8R5                          |
|           |                                                          |
|           | Attention:                                               |
|           |                                                          |
|           | The migration procedure will set the file ownership and  |
|           | permissions to match your previous configuration.        |
|           | Verify that the mount point directory is owned by your   |
|           | WebSphere Application Server administrator and that the  |
|           | group is assigned to the Administrators group. If it is  |
|           | not, then determine the user ID and group ID values that |
|           | are designated as owners of the previous WebSphere       |
|           | Application Server configuration. Either the numeric ID  |
|           | values or the user name and group name can be used.      |
|           | Issue the following command within the OMVS shell,       |
|           | replacing <user> and <group> with the user and group     |
|           | determined previously. Also replace <mountpoint> with    |
|           |                                                          |
|           | &MBMOUNTP.                                               |
|           |                                                          |
|           | chown <user>:<group> <mountpoint>                        |
|           |                                                          |
)ENDSEL
+-----------+----------------------------------------------------------+
| BBOWMG1F  |                                                          |
+-----------+ This job must be submitted from a WebSphere              |
|           | Application Server administrator's user ID.              |
| Done:     |                                                          |
|           | 1. Stop the application server.                          |
|           |                                                          |
| By:       | 2. Submit the job, and verify that the return code is 0. |
|           |                                                          |
|           | 3. Restart the application server, and wait for it to    |
|           |    perform PRR processing and terminate.                 |
|           |                                                          |
|           | 4. If the server does not terminate after a few minutes, |
|           |    stop the server.                                      |
|           |                                                          |
|           | This job is not required if you do not have any XA       |
|           | connectors installed in your prior server. If you have   |
|           | any XA connectors, submit this job.                      |
|           |                                                          |
+-----------+----------------------------------------------------------+
| BBOWMG2F  |                                                          |
+-----------+ This job must be submitted from a WebSphere              |
|           | Application Server administrator's user ID.              |
| Done:     |                                                          |
|           | 1. After completing BBOWMG1F, submit this job.           |
|           |                                                          |
| By:       | 2. Submit the job, and verify that the return code is 0. |
|           |                                                          |
|           | This job is not required if you do not have any XA       |
|           | connectors installed in your prior server. If you ran    |
|           | BBOWMG1F, you must submit this job.                      |
|           |                                                          |
+-----------+----------------------------------------------------------+
| BBOMMCP   |                                                          |
+-----------+                                                          |
|           | &MBPROCL.                                                |
| Done:     |                                                          |
|           | Attention:                                               |
|           |                                                          |
| By:       | WebSphere Application Server Version 8.5 requires        |
|           | new STARTED procedures that you provided when you        |
|           | created your migration definition.  Depending on what    |
|           | these are, you might be required to create additional    |
|           | RACF STARTED profiles.                                   |
|           |                                                          |
|           | It is recommended that you use the same user ID and group|
|           | memberships that you used in your previous version.      |
|           | If you are using the same PROC as identified in the      |
|           | deployment manager process, you do not need to run this  |
|           | job.                                                     |
|           |                                                          |
|           | This job copies the tailored start procedures,           |
|           | parameters, and EXECs to the runtime libraries.          |
|           |                                                          |
|           | Be aware that you might overlay existing members in      |
|           | the above data set.                                      |
|           |                                                          |
|           | If you previously configured the transaction XA partner  |
|           | log or compensation log on the Version 5.1.x or 6.x      |
|           | server to use a log stream, delete and redefine the log  |
|           | stream before proceeding.                                |
|           |                                                          |
|           | -  Make sure that the node is shut down.                 |
|           |                                                          |
|           | -  You can use the BBOLOGSD and BBOLOGSA jobs that were  |
|           |    created during Version 5.1.x or 6.x customization if  |
|           |    you configured the server initially to use the log    |
|           |    stream.                                               |
|           |                                                          |
|           | If you are migrating nodes in a sysplex, follow this     |
|           | procedure for each federated node that you migrate.      |
|           |                                                          |
+-----------+----------------------------------------------------------+
| Select    | The job or jobs in this step must be submitted from a    |
|===========| WebSphere Application Server administrator's user ID.    |
|           | Select whether to use the single or multi job option.    |
| Option 1  |                                                          |
| --------  | 1. The Version 8.5 deployment manager must be started    |
| BBOWMG3F  |    before submitting this job.                           |
|           |                                                          |
|-----------| 2. Submit the job, and verify that the return code is 0. |
|           |    If using the multi-job option verify the return code  |
| Option 2  |    is 0 before submitting the next job.                  |
| --------  |                                                          |
| BBOWMPRO  | This step performs the main migration procedure. Based   |
| BBOWMPRE  | on the information that you provided when you created    |
| BBOWMPOS  | your migration definition and your existing              |
|           | configuration, your previous server will be migrated     |
+===========+ to Version 8.5.                                          |
|           | The migration steps include:                             |
| Done:     |   1) creating a target profile in the new release.       |
|           |   2) creating a backup of the source profile.            |
|           |   3) migrating the backup profile into the new profile.  |
| By:       | All three steps can be done using a single job:          |
|           |                BBOWMG3F                                  |
|           | OR they can be individually submitted in this order:     |
|           |      BBOWMPRO, BBOWMPRE, BBOWMPOS                        |
+-----------+----------------------------------------------------------+
|           | Permit the servant's user ID read access to the z/OS     |
| Done:     | Workload Manager (WLM) server profile.                   |
|           |                                                          |
|           | WebSphere WebSphere Application Server for z/OS Version  |
| By:       | 8.5 requires that the servant's address space be         |
|           | authorized to interface with WLM. The following RACF     |
|           | commands must be issued to permit the application        |
|           | server's STARTED tasks user ID to have READ access to    |
|           | the WLM server profile:                                  |
|           |                                                          |
|           |  PE BPX.WLMSERVER CLASS(FACILITY) ID(<servant_user_id>)  |
|           |      ACCESS(READ)                                        |
|           |  SETROPTS RACLIST(FACILITY) REFRESH                      |
|           |                                                          |
+-----------+----------------------------------------------------------+
| --------  | All WebSphere Application Server processes require       |
+-----------+ access to the Language Environment and System SSL load   |
|           | modules.                                                 |
| Done:     |                                                          |
|           | If the SCEERUN, SCEERUN2, and System SSL load module     |
|           | libraries are not in the system link list or link pack   |
| By:       | area, add them to the STEPLIB DD concatenation in each   |
|           | of the following cataloged procedures in                 |
|           |                                                          |
|           | &MBPROCL.:                                               |
|           |                                                          |
|           |     &MMCPN                                               |
|           |     &MMSPN                                               |
|           |     &MMDPN                                               |
|           |                                                          |
|           | and also add the full data set names, separated by       |
|           | colons (:), to the STEPLIB variable in the shell script  |
|           |                                                          |
|           |     &MMMOUNTP./                                          |
|           |     &MMDIRN./                                            |
|           |     profiles/default/bin/setupCmdLine.sh                 |
|           |                                                          |
|           | When modifying the setupCmdLine.sh script, do not        |
|           | remove lines or comment them out, as this might cause    |
|           | problems with automated updates to the script.           |
|           |                                                          |
|           | Add only those data sets that are NOT in the link list   |
|           | or link pack area.                                       |
|           |                                                          |
+-----------+----------------------------------------------------------+
|           | Shut down the application servers and daemon.            |
| Done:     |                                                          |
|           | If you already restarted the daemon and deployment       |
|           | manager at Version 8.5 during the deployment manager     |
| By:       | migration steps, then ONLY shut down the application     |
|           | servers and node agent before running this job.          |
|           |                                                          |
|           | The daemon is required to run at the Version 8.5 level   |
|           | of code for all the servers that it manages on the same  |
|           | LPAR. It will be at the Version 8.5 level when this      |
|           | federated node is started.                               |
|           |                                                          |
+-----------+----------------------------------------------------------+
| Done:     | Copy unrestricted jurisdiction policy files              |
|           |                                                          |
|           | If you saved a copy of local_policy.jar in the           |
|           | beginning of the migration process take the following    |
| By:       | steps:                                                   |
|           | 1)After migration completes successfully, mount the new  |
|           | product hfs read/write.                                  |
|           | 2)Copy the modified local_policy.jar from the temporary  |
|           | location to the following directory on the new WebSphere |
|           | Application Server installation:                         |
|           | WAS_HOME/java/lib/security                               |
|           | 3)Mount the new product HFS as read/only                 | 
|           |                                                          |
|           |                                                          |
+----------------------------------------------------------------------+
|           | Start the application server.                            |
| Done:     |                                                          |
|           | Use the existing commands that you currently use         |
|           | to start your previous server, but replace the STARTED   |
| By:       | procedure name with the value that you entered when you  |
|           | created your migration definition.                       |
|           |                                                          |
|           | &MMCPN.                                                  |
|           |                                                          |
|           | This command starts the application server. Wait until   |
|           | the server has finished initializing before proceeding.  |
|           |                                                          |
|           | The following message appears on the console and in the  |
|           | job log of BBOS001:                                      |
|           |                                                          |
|           |   BBOO0019I INITIALIZATION COMPLETE FOR WEBSPHERE FOR    |
|           |   z/OS CONTROL PROCESS BBOS001                           |
|           |                                                          |
+-----------+----------------------------------------------------------+
|                                                                      |
| Migration has now been completed.                                    |
|                                                                      |
+----------------------------------------------------------------------+





