Message Security violation when placing a program under Date Simulator control issuing a WARPPARM SET command.
Article ID: 245902
Updated On:
Products
Issue/Introduction
When placing the Date Simulator installation verification program TIMECOB under Date Simulator control issuing the WARPPARM SET command the programmer receives the following message
*0001: TIMECOB :Security violation
Below is sample JCL using the Date Simulator WARPPARM utility SET command for program TIMECOB to use a future date of 01/01/2031.
//WARPDATE EXEC PGM=WARPPARM
//SYSOUT DD SYSOUT=*
//SYSIN DD *
SET JOB TIMECOB CURRENT DATE 01/01/2031 -
STCK(CEEPLPKA,01FA414 CEEPLPKA,01FA5F0,CEEPLPKA
/*
//*
The test program runs to a successful completion but the current date is used and not the future date of 01/01/2031.
Environment
Z/OS
Date Simulator release 2.0
Cause
Date Simulator does not ship with a security exit load module. This site created a custom security exit program WARPSCTY and the installers User ID did not have authorization to issue Date Simulator SET commands.
Resolution
The user will contact the security administrator and request access to Date Simulator.
When Date Simulator starts, it attempts to load a module named WARPSCTY from its APF-authorized load library. If the load is successful, Date Simulator calls WARPSCTY each time a SET, RESET, or CLEAR command is issued.
As a work around the security exit program WARPSCTY was renamed to WARPSCTX so the load of the security exit would fail. Date Simulator was then stopped and restarted without a security exit. This removed security from Date Simulator and allowed the installer to verify the product installation. Once the installation was verified, load module WARPSCTX was renamed back to WARPSCTY and Date Simulator was recycled.
For additional information please review the Date Simulator User's Guide Chapter 5 topic Provide a User Security Exit.
Feedback
