Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

facebook Twitter
Email
Print Bookmark Alert me when this article is updated

Feedback

HOW TO: Rename the PowerExchange Logger datasets on MVS
Solution

Please follow the steps given below to rename the logger datasets:

Step 1. Stop the ECCR

    Step 2. Create an original report of the PowerExchange logs

    Run the following command and save the output for later reference:

    /f loggername,DISplay OBJECT=LOG,type=all,dsname=*

    This command will display all active and archived logs and the active log set that is being used at any given time. 
    At the far right of the display you will see STATUS IN-USE.
    At the left of the display you will see the RBA information for each dataset.

    Example

    REPORT will look something like this:

    10:04:42.37 PWXEDM172679I EDM Logger LOG ALL report follows:
    10:04:42.37 *Start RBA End RBA Log Dsname Status
    10:04:42.37 00298F614000 0029BB533FFF DSNVS.PROD.INFA.PRILOG.DS01 REUS
    10:04:42.37 0029BB534000 0029E7453FFF DSNVS.PROD.INFA.PRILOG.DS02 REUS
    10:04:42.37 0029E7454000 002A13373FFF DSNVS.PROD.INFA.PRILOG.DS03 REUS,IN-USE     <=====CURRENT ACTIVE
    10:04:42.37 002A13374000 002A3F293FFF DSNVS.PROD.INFA.PRILOG.DS04 REUS
    10:04:42.37 0029636F4000 00298F613FFF DSNVS.PROD.INFA.PRILOG.DS05 REUS
    10:04:42.37 00298F614000 0029BB533FFF DSNVS.PROD.INFA.SECLOG.DS01 REUS
    10:04:42.37 0029BB534000 0029E7453FFF DSNVS.PROD.INFA.SECLOG.DS02 REUS
    10:04:42.37 0029E7454000 002A13373FFF DSNVS.PROD.INFA.SECLOG.DS03 REUS,IN-USE    <=====CURRENT ACTIVE
    10:04:42.37 002A13374000 002A3F293FFF DSNVS.PROD.INFA.SECLOG.DS04 REUS
    10:04:42.37 0029636F4000 00298F613FFF DSNVS.PROD.INFA.SECLOG.DS05 REUS
    10:04:42.37 *Start RBA End RBA Log dsname *
    10:04:42.37 001890CB4000 0018BCBD3FFF DSNVS.PROD.INFA.PXPL.LG1.D2006284.T1318452

    In this example there are 5 primary and 5 secondary logs and several archive logs that are not included here.

    In the following process you will start by deleting 4 Primary and 4 Secondary logs and adding 5 new Primary and 5 new Secondary logs. 
    The IN-USE Currently Active logs will also be deleted using these steps. 
    They will be deleted later in these steps when the Logger is restarted and the logs are rolled over to the new log datasets.

    Step 3. STOP the PowerExchange Logger

    Stop the PowerExchange Logger when the ECCR are stopped.
    You have to make changes to the Logger which requires it to be stopped.

    Step 4. Change the archive options for the logger. 

    This is to prepare the Logger to start using the new dataset names for the archive logs.
    In Runlib there is a member called SETUPCC2. 
    ONLY USE THE FIRST STEP OF THIS JOB. 
    Only change the PREFIX_COPY1 and PREFIX_COPY2 under the ARCHIVE_OPTIONS section.
    You need to execute this job after you make the appropriate changes. 
    Again this should be the member that was executed originally to create your Logger.
    If your site used different JCL then please refer to it. 
    But only use the step which allows you to change the options for the Logger.

    Step 5. Create and format the new active logs

    In Runlib there is a member called XICDC500. 
    This is how the logs were originally created unless your site has changed and used a different set of jcl. 
    Make a copy of the installation JCL and change the names as required. 
    This job will create the 5 new Primary and 5 new Secondary datasets and then format all 10 for the Logger. 
    The datasets you create will be:

    hql.PRILOG.DS01
    hql.PRILOG.DS02
    hql.PRILOG.DS03
    hql.PRILOG.DS04
    hql.PRILOG.DS05
    hql.SECLOG.DS01
    hql.SECLOG.DS02
    hql.SECLOG.DS03
    hql.SECLOG.DS04
    hql.SECLOG.DS05

    Step 6. Define the 10 new log sets into your existing pwx environment using the following.

    Create a DEFINE_LOG for each primary and each secondary log. 
    Be sure to specify the COPY= accordingly.

    //*--------------------------------------------------------
    //* DEFINE ACTIVE LOG DATA SETS TO EDM LOGGER
    //*--------------------------------------------------------
    //DEFLOG   EXEC PGM=EDMLC000,PARM='loggername,BATCH'
    //STEPLIB  DD DISP=SHR,DSN=hlq.LOAD
    //EDMPARMS DD DISP=SHR,DSN=hlq.loggername.USERLIB
    //ERDS01   DD DISP=SHR,DSN=hlq.V1.loggername.ERDS01
    //ERDS02   DD DISP=SHR,DSN=hlq.V1.loggername.ERDS02
    //SYSPRINT DD SYSOUT=*
    //SYSUDUMP DD SYSOUT=*
    //SYSIN    DD *
    DEFINE_LOG
        DSNAME=hlq.PRILOG.DS01,
        COPY=PRILOG  <=====for a PRImary log  *******
    END
    DEFINE_LOG
        DSNAME=hlq.SECLOG.DS02,
        COPY=SECLOG  <=====for a SECondary log  *****

    Step 7. Run the following JCL to produce the Logger Report:

    //*-------------------------------------------------------------------*
    //* EXECUTE THE DISPLAY REPORT WHILE THE LOGGER IS NOT RUNNING
    //*-------------------------------------------------------------------*
    //DEFLOG   EXEC PGM=EDMLC000,PARM='loggername,BATCH'
    //STEPLIB  DD DISP=SHR,DSN=hlq.LOAD
    //EDMPARMS DD DISP=SHR,DSN=hlq.loggername.USERLIB
    //ERDS01   DD DISP=SHR,DSN=hlq.V1.loggername.ERDS01
    //ERDS02   DD DISP=SHR,DSN=hlq.V1.loggername.ERDS02
    //SYSPRINT DD SYSOUT=*
    //SYSUDUMP DD SYSOUT=*
    //SYSIN    DD *
    DISPLAY OBJECT=LOG,
    TYPE=ALL,DSNAME=*
    END
    /*
    //

    What to check in this report:

    • The old primary and secondary active logs are there with the IN-USE status
    • The new primary and secondary active logs are defined
    • The old primary and secondary active logs will still be there (you will not see any of the new archive datasets in this list because none have been created yet using the new name).

    Step 8. Start the Logger and the ECCR

    If all looks correct from the last Report then Start the Logger and the ECCR and go to step 9.

    Step 9. Run the Logger report

    Now that the Logger and ECCR are back up and running use the Logger report command to continue watching to see when one of  the new log dataset pairs become the IN-USE datasets. 
    Timing depends on the environment.
    It will roll off of the old log datasets and on to the new log datasets as the logs become full and archive and so on. 
    When this happens you can do the following.

    You do not have to stop the logger in order to do this. 
    If you are attempting this when there is a lot of data being processed you might have to wait until another time when there is little activity. 
    If you do not have such a time then you will need to bring the ECCR back down and run the following using JCL instead of from the command line.

    Run the following for the logger report:

    f loggername,DISplay OBJECT=LOG,type=all,dsname=*

    Check to see all of the datasets are in place including the most recently created archive logs.
    Check to see the old logs are no longer IN-USE.

    Once all is verified and from the command line in extended mode do the following:

    1. Delete the old primary log from the command line:

      F loggername,DELETE_LOG DSNAME=oldhlq.V1.PRILOG.DS0#

    2. You will see the following message at the bottom of the Logger job:

      PWXEDM172576I EDM Logger DEL_LOG command complete for WTOR (task1), with RC=0000

    3. Verify the log has been deleted and all other logs are in place:

      F loggername,DISplay OBJECT=LOG,type=all,dsname=*

    Repeat steps 1-3 for each of the old log primary and secondary datasets.

    From here just wait for the old archive logs to cycle out of the system.
    Your PWX environment should be using all new names at this point.
    Remember the old active logs are not deleted from MVS by this process.
    This process deletes only the definitions from the PWX environment.

    More Information
    You should also ensure that, if renaming a Logger, the CAPI Connection, TYPE=LRAP, and LOG= is changed to reflect the new name, else your extractions may fail with Logread failure A0E0063.
    Reference
    Applies To
    Product: PowerExchange
    Problem Type:
    User Type:
    Project Phase:
    Product Version: PowerExchange
    Database:
    Operating System: OS/390 (MVS/zOS)
    Other Software:
    Attachments
    Last Modified Date:12/29/2011 9:51 PMID:114048
    People who viewed this also viewed

    Feedback

    Did this KB document help you?



    What can we do to improve this information (2000 or fewer characters)