By using this solution, you can transfer entire job classes to another system. If you must  transfer output elements to another system but must keep the old destination, you cannot use  JES2 system commands. The use of these commands results in loosing such information. An  example in which a simple REXX program is used is shown in Example 6-25. Example 6-25 REXX for transferring output /*REXX================================================================*/  /* Purpose: Transfer all Output elements located in Sysout class 2 */  /* to sysplex PLEXQ and keep to old destination (the old */  /* printer name). */  /* */  /* History: 14.06.18 LK Initial for ITSO Redbooks  */  /* */  /*====================================================================*/   rc = ISFCalls('ON')  ISFPrefix = "**"  ISFOwner = "**"  DestPlex = 'PLEXQ'  Address SDSF "ISFEXEC O"  Do i=1 to JNAME.0 if SCLASS.i = '2' Then Do Address SDSF "ISFACT O TOKEN('"TOKEN.i"')", "PARM(DEST" DestPlex!!"."!!DEST.i")" End End rc = ISFCalls('OFF')  exit The differences while transferring output to another system by using the JES2 command and  the REXX program are listed in Table 6-17. Table 6-17 DEST comparison Output element at origin In PLEXQ with $TOJOBQ  command In PLEXQ with the REXX  program DEST=B433 DEST=LOCAL DEST=B433 Change this REXX program to suit your needs and place it in your system automation based  on your needs. The program should run with more or less frequency. Complete the following steps to migrate your security definitions to a JES2 version: 6.9 Migrating security 1. Convert existing JES3 prefixed profiles in RACF to a JES2 prefixed profile. The following  RACF classes are affected: – Class NODES and WRITER for NJE and RJE definitions – JESINPUT for offloading – JESSPOOL for controlling job permissions Chapter 6. Customer experience case study  157