A fix is available
APAR status
Closed as program error.
Error description
You attempt to use the IMPORT option in transaction COVC to import WUI (Web User Interface) views, menus, etc. but the import fails and you receive the following message . EYUVS0917E Import operation failed . If you take a look at the exception user trace records that get written to either the internal trace table or to the WUI's AUX trace datasets, you would see something like the following: . Task Mtd Prev Tran Obj Level Pt-ID Debug UOW CMAS/Usr 12345 VVIC VVIE COVC SIM Excp 62 BadVVID CPSM <applid> 12345 VVIE VCTW COVC SIM Excp 2 badVVIC CPSM <applid> . The actual VVID method COMMAREA is traced on the data from the second trace entry, and you can see that VVID had a return code of x'00000010' and visually you can see the text 'BadWrte1' in the data traced. . This has happened because CICS has attempted to issue an EXEC CICS WRITEQ_TS and received RESP=53 RESP2=4. A RESP value of 53 indicates SYSIDERR. RESP2 value of 4 in this case can occur, among other reasons, if you have defined a TSMODEL with a POOLNAME in the CICS region, but the region can not connect to the TS Server (because it's not running or the region is not authorized to use it.) . In the CICS job log, you may also see message AXMSC0032 similar to the following . AXMSC0032 Connection to server DFHXQ.poolname failed because the server was not found. . If your TSMODEL does not specify a POOLNAME, but you have Temp Storage security turned on via SIT parameter XTST, the message on the screen will be the same, but the ICH408I (if you use RACF) security violation messages in the WUI job log will clearly indicate a security failure against profile EYU0VVID in the SCICSTST class. Trace in this case will show a number of security failures on the Temp Storage queue name EYU0VVID. . Additional Symptom(s) Search Keyword(s): KIXREVSCB
Local fix
Start the TS Server, correct security problems, or remove the TSMODEL which matches queue name EYU0VVID.
Problem summary
**************************************************************** * USERS AFFECTED: All CICSPlex SM V5R2M0 Users * **************************************************************** * PROBLEM DESCRIPTION: When importing CPSM Web User Interface * * (WUI) viewsets, the operation can fail * * with the "EYUVS0917E Import failed" * * message, but without any supporting * * detail in the CICS or CPSM message * * logs. * * * **************************************************************** * RECOMMENDATION: After applying the PTF that resolves this * * APAR, all affected WUI regions must be * * recycled to pick up the new code. * * * **************************************************************** One of the options available for importing WUI Viewsets is to take them directly from a member in an MVS partitioned dataset (PDS). When importing a PDS member, module EYU0VVID extracts the viewset content into a temporary storage queue. This queue is passed forward to module EYU0VVIC, which takes that data and amalgamates it into the EYUWREP dataset. When the import process starts, an internal TS Queue (named "EYU0VVID") is deleted prior to being rewritten. If any TS errors are returned from CICS when processing this TS queue, then the import operation is aborted, but the reasons for the TS errors are not exposed through any CICS message log. That detail must be extracted from the CICS auxiliary trace dataset and interpreted by IBM support staff.
Problem conclusion
Any DELETEQ TS and WRITEQ TS errors from the CICS API are now captured by EYU0VVID. These error codes are subsequently interpretted by EYU0VVIC and reported to the EYULOG through new message EYUVS1074E: 'EYUVS1074E - Internal CICS DELETEQ|WRITEQ TS command has failed with response code (RESP/RESP2).' The RESP value will be displayed as its CICS API command response name (INVREQ, SYSIDERR, etc), but the RESP2 value will be displayed in its native numeric format. If the import process is unable to interpret the RESP value, then the RESP and RESP2 values are printed in their raw hexadecimal representation - as returned from the CICS API. The reported response code should then be checked against the reported CICS command in the CICS Application Programmers Reference, or the IBM Knowledge Centre, to determine the reason for the reported command failure.
Temporary fix
FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PI47986
Reported component name
CICS TS Z/OS V5
Reported component ID
5655Y0400
Reported release
90M
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-09-01
Closed date
2015-12-01
Last modified date
2016-01-27
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI33442 PI56132
Modules/Macros
EYUEVVEI EYUKVVEI EYUSVVEI EYU0VVIC EYU0VVID EYU0VVIE
Fix information
Fixed component name
CICS TS Z/OS V5
Fixed component ID
5655Y0400
Applicable component levels
R90M PSY UI33442
UP15/12/04 P F512
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
27 January 2016