This action might not be possible to undo. Are you sure you want to continue?
Ed Addison IBM Session Number 1225
PM02187 provides new Web 2.0 samples for Atom support in CICS TS V4.1
• New Function (NF) APAR PM02187 supplies new sample programs and other files for several new Web 2.0 scenarios that demonstrate how to set up Atom feeds in CICS Transaction Server for z/OS (CICS TS) V4.1. This APAR also fixes a storage overlay problem that can occur in certain situations. APAR PM02187 closed on 1 February 2010. To take advantage of this new functionality, see APAR PM02187 for CICS TS V4.1 then apply the PTFs provided with the APAR. The CICS TS V4.1 information center has been updated to add three new scenarios to the Web 2.0 scenarios section. These scenarios are:
• • • Creating an Atom feed from unstructured data in a temporary storage queue Creating an Atom feed from a file Creating an Atom feed from structured data in a temporary storage queue
The topic 'How the Atom sample works' has been updated to include these additional artifacts.
CICS TCP/IP port hangs until CICS is recycled after applying PTFs for OMVS APAR OA29566
• You are using CICS Transaction Server for z/OS (CICS TS) and TCP/IP. Your CICS TCP/IP port hangs and is not responding. There are no errors but all work on that PORT ceases. You have to bring CICS down and back up to resolve the problem. This occurs after you apply OMVS PTF UA51856 (z/OS V1.9), UA51857 (z/OS V1.10), or UA51830 (z/OS V1.11) for APAR OA29566. Severity 1 OMVS APAR OA32088 has been open to address this problem. If possible, you should not apply the PTFs for APAR OA29566 until the PTFs for OA32088 become available. If you did APPLY one of the PTFs, REJECT it to back it off. You will also have to IPL to remove the PTF which is in error.
New CICS TS 4.1 Abend AFDK
• A file control request was made against a NSR file while transaction isolation was active for the task. Using NSR files with transaction isolation active is not supported. The TRANISO system initialization parameter is YES and the transaction definition has ISOLATE set to YES. VSAM nonshared resources (NSR) are not supported for transactions that use transaction isolation. You should specify ISOLATE(NO) when you define transactions that access VSAM files using NSR.
• CICS Manuals at all supported releases indicate:
NOTE: CICS OPEN APAR PM07304 will allow READONLY Files to use NSR and Transaction Isolation.
DFHSI1596 AFTER RUNNING DFH$UMOD • You run DFH$UMOD to add DFHLETRU to the LPA. DFHLETRU is also a member of the CICS Nucleus and receives error message DFHSI1596 and ABENDU1800 causing CICS to terminate. • Monitor OPEN APAR PM08478 • Move DFHLETRU back to SDFHLOAD .
All of your libraries have equal ranking of 50.Ranking order of Dynamic Library • You are implementing dynamic library management. the order of the libraries have been changed to alphabetical. and auto restart (warm). After a normal shutdown. within rank. You expect the order of the libraries to remain same after warm or emergency restart. • See APAR PK85333 / PTF UK46963 . • DFHLDDMI has been altered to add the libraries to the chain of library elements by order of creation time.
The ABEND0C4 is occurring in CA module CASECPRM. You receive an abend0C4 during CICS startup while loading the System Initialization Table (SIT).ABEND0C4 loading DFHSIT in CICS TS 4. Apply the following CA fixes for CA Common Services: QO94573 QO94574 QO99498 RO08960 RO08982 • • .1 and are running with CA Common Services. The problem occurs after message DFHPA1101 DFHSIT IS BEING LOADED.1 with CA Common Services • You have just installed CICS Transaction Server for z/OS (CICS TS) V4. You also see message IEA995I indicating that an 0C4 abend has occurred. The CICS region still comes up and is available.
If you want to know why your normal shutdown is not completing 'normally' then you can code SDTRAN=NO. NOTE: You will receive CICS message DFHTM1703 if CESD issues an Immediate Shutdown • 8 .Shutdown is immediate when SDTRAN=CESD • Problem: During shutdown of your region. See MustGather: Documentation for a wait or loop in CICS for details on how to get the dump if needed. you will be able to review what tasks are active that are keeping CICS from shutting down. commit-failed or backout-failed UOWs. • Solution: Take the steps necessary to prevent the shutdown assist program from turning your normal shutdown into an immediate shutdown. you do not receive message DFHRM0204 There are no indoubt. This is due to an immediate shutdown occurs when you specify SDTRAN=CESD in your CICS® system initialization table (SIT). Afterwards. This will cause CICS shutdown to hang if it can not be completed normally.
DFHSMMC2 is called to perform INQUIRE_TASK_STORAGE.CICS TS 3. – The code in DFHSMMC2 needs to call XM to return transactional information. so requires the XMLOCK • DFHSMMC2 has been changed to release and reacquire the SMLOCK around the calls to transaction manager for this operation • Apply APAR PK65070 / PTF UK38082 9 . so it waits for SMLOCK. and another that owns XMLOCK and is waiting for SMLOCK – CICS has attached the CJGC transaction to perform Java garbage collection work. This holds the SMLOCK within DFHSMMC2 – The attach of CJGC requires storage.2 DEADLOCK AFTER TWO USER TASKS WANT SMLOCK AND XMLOCK • There is a deadlock between a transaction that owns the SMLOCK and is waiting for the XMLOCK to be freed. The XMAT attach logic requires the XMLOCK while it does its work – Another task is issuing an EXEC CICS INQUIRE STORAGE call.
• Solution: Apply CA Top Secret PTF QO44619. . No other users can signon or signoff while this lock is being held • Cause: The lock owning task was stuck in a CAKSSIGN wait in CA module CAKS62SK. Contact CA if you need additional assistance.USADLOCK held by one task and no signons occur • Problem: You have one user in your CICS Transaction Server region who is hung and holding the USADLOCK. This locks the User Domain table during signon or signoff to add or delete a user ID.
2 .PK74824 / UK44271 – CICS Transaction Server for z/OS V3.PK80416 / UK44241 – CICS Transaction Server for z/OS V3.PK74824 / UK44272 .ADCF USING IMS PCBLOC=31 AND AMDODE 31 PROGRAMS • An unexpected abend ADCF occurs when running an AMODE 31 CICS application with IMS v10 and PCBLOC=31 is specified. only EXEC DLI • CICS APARs / PTFs: – CICS Transaction Server for z/OS V2.3 . • CALLDLI applications are not affected. An abend ADCF is expected if the CICS application is running AMODE 24.1 . DFHDLIDP issues the abendADCF because TCAAAM31 is not set to indicate this is an AMODE31 application.
• CICS Toleration PTFs: – CICS Transaction Server for z/OS V2.3 .1 . During a PSB schedule request. CICS checks to see if PCBLOC=31 is in effect and the application is amode 24. so the application is abended with a new abend code ADCF. • When CICS connects to DBCTL.UK30300 . If.IMS V10 New PCBLOC=31 Support • IMS V10 DRA startup table option PCBLOC=31 causes the PCB address list and the PCBs to be placed above the 16MB line.UK30295 – CICS Transaction Server for z/OS V3. IMS returns an indicator if PCBLOC=31 is in effect.2 .UK30299 – CICS Transaction Server for z/OS V3.
• You can use the sample utility program DFH$STED to vary the end-of-day time of each CICS region it is installed in.ibm.boulder.com/infocenter/cicsts/v3r2/index. and therefore vary the interval occurrence time of these CICS regions. you should vary the statistics interval occurrence time for each CICS region.html .jsp?topic=/com. • The source code for DFH$STED is supplied in the SDFHSAMP samples library.doc/dfha6/topics/dfha62o.cics.ts.Performance Hit End of Day Statistics • Statistics intervals can occur simultaneously across many CICS regions in the same z/OS image. and this can degrade performance.ibm. and the pregenerated version is supplied in SDFHLOAD • More Information at: http://publib. To prevent this.
and the request becomes orphaned • SMSVSAM on the offending system needs to be terminated with V SMS.SMSVSAM.TERMINATESERVER command in order for the Quiesce / Unquiesce events to be cleared up • Monitor Open SMSVSAM APAR OA25890 .SMSVSAM Quiesce / Unquiesce Events Orphaned • Errors in SMSVSAM RLS module IDAVQSXT can lead to Quiesce / Unquiesce events being orphaned • While Performing a Quiesce / Unquiesce event an error in the code path of IDAVQSXT can lead to a cancel event being issued. However there is a problem where this cancel does not complete.
2 and RLS Datasets only • CICS APAR PK69224 describes this issue • PTF UK38575 .AFCS ABEND Using RLS • AFCS Abend and Dataset will not close after SMSVSAM Terminate / Reactivate Server • CICS TS 3.
It must now be explicitly set to enable threadsafety. The default will now be FCQRONLY=YES. This will affect RLS threadsafety if the SIT parameter had been allowed to default to FCQRONLY=NO. .2.Local File Control threadsafe support in CICS TS V3.2 will be disabled • Problem: Threadsafe File Control support for local VSAM will be disabled at General Availability (GA) of CICS® Transaction Server for z/OS® V3. The function will be enabled by APAR PK45354 / PTF UK37688 • Solution: The purpose of the disablement is to ensure that a full system test of this critical function is completed • You will need APAR PK45354 / PTF UK37688 to enable Threadsafe File Control for local VSAM LSR • VSAM APARs OA20352 and OA24071 must be applied • The SIT parameter FCQRONLY has been changed.
storage becomes orphaned. DFHEITAB has been altered to issue a RC 12 when CHANNEL is specified without TRANSID on a EXEC CICS RETURN command Reference R310 / R320 APAR PK86108 or R410 APAR PK89132 • • • . The CICS Translator should have generated an error against this command as the manual states that CHANNEL is a sub-parm under TRANSID.CICS orphaning Channels and Containers • Application is issuing EXEC CICS RETURN CHANNEL. This is causing the task's associated channel and containers to be detached but never freemained. Each time this command is issued. CHANNEL can only be specified if TRANSID has been specified as well During the Translation. This eventually leads to CICS going short on storage and issuing the message DFHSM0133 The root problem is the EXEC CICS RETURN CHANNEL.
unless the files are actually on the MASTER. You have granted the CICS USERID access to the USER catalog per APAR PK68899. Since you do not have any CICS files on the MASTER you did not grant access.DFHFC0519 DFHFC0304 Master Catalog Security Error when opening Dataset • You have put all of you CICS FILES on a USER catalog. You still get the DFHFC0519 and DFHFC0304 message for the MASTER catalog. • Reference APAR PK76647 . • CICS should not access the MASTER catalog. they are not on the MASTER.
• Resolving the problem: Contact CA for fix number T32D604. . Your CICS region might also abend AEXZ or hang. You are running CA Intertest.DFHSM0002 code x'030D' invalid_QPF getmain IN25TRUE • Problem: Your CICS Transaction Server for z/OS (CICS TS) region issues message DFHSM0002 severe error code X'030D' in module DFHSMGF. • Symptom: DFHSM0002 A severe error (code X'030D') has occurred in module DFHSMGF.
2 APAR PK85198 PTF UK48737 See 4. You have an application program defined as EXECKEY(USER) and Concurrency ( Threadsafe ). EZACIC01 (which is enabled as OPENAPI.) the program runs in basespace rather than in subspace • DFHERM has been modified to avoid the switch to BASESPACE when calling an OPENAPI TRUE.1 APAR PK90945 PTF UK48726 .Running in BASESPACE after call to TRUE • You are using Tranaction Isolation. • • See 3. Following a call to the CICS/TCPIP Sockets TRUE.
• Reference APAR PK86331 – R500 UK50353 – R600 UK50391 .Recoverystatus for RLS Files • RLS file shows that RECOVERY REQUIRED=NO. • CICS should use the VSAM ICF Catalog for all inquiries of a RLS dataset. • If the file is OPEN ENABLED for readonly then CICS SPI returns a value of RECOVERYSTATUS based on the RDO definition instead of what is defined on the VSAM ICF Catalog.
CICS Region Stall using ICSF • Using Integrated Cryptographic Services Facility (ICSF) to encrypt and decrypt data within a CICS region can cause the address space to stall if not properly setup • You should have the WLM class for ICSF as high or higher as CICS • You MUST have the ICSF TRUE (CSFATRUE) installed in the CICS region to ensure the crypto work is sub-tasked off the QR TCB .
After an Upgrade to CICS TS V3. The request has failed.2 you receive the following messages when accessing the dataset: – DFHFC6037I Program xxxxxxxx has issued an RBA request against an extended addressing ESDS data set – DFHFC6038 Program xxxxxxxx has issued an unsupported type of RBA request against an extended addressing ESDS. – 2. • Extended ESDS support was introduced in CICS TS V3.New messages when accessing Extended ESDS • You have a program that accessed an Extended ESDS in CICS and it worked fine. Especially if you don’t ever plan to go over 4G. Prior to this release.0008.2 you may: – 1.0068 • At CICS TS V3. Define the dataset as a regular ESDS like it should have been. if you accessed an Extended ESDS it would sometimes work and sometimes fail with DFHFC0966 with return code 8504. Change the application to use XRBA .2.
2 an application receives low value WebSphere MQ messages after going through data conversion • WMQ messages which have been processed by the WMQ data converter. This is due to the addresses belonging to the L8 TCB upon which the data conversion table was originally loaded being invalid • A new CICS/WMQ module DFHMQLTT has been introduced which will switch to the QR TCB prior to issuing the load of the WMQ translate table • CICS R500 APAR PK58227 / PTF UK34407 • WebSphere MQ for z/OS V6 APAR PK59397 / PTF UK34250 • WebSphere MQ for z/OS V5.1 APAR PK59405 / PTF UK34261 .ABEND0C4 / ABEND0C1 in DFHMQTRU • After migrating to CICS TS 3.3. are arriving as low value messages.
2 to CICS TS V2.3 and above. Any daughter TCBs of the QR are now dubbed as a process. • Cause: The way CICS TCBs were dubbed was changed in CICS TS V2. "TCPIP Sockets for CICS" can use up to 300-400 TCBs at any time. These TCBs are not OPEN TCBs but rather use Unix System Services (USS). For instance.2 they are counted • Solution: Increase the value specified for MAXPROCUSER • Related information: Review Documentation APARs PK02033 and PK04602 for explanation of TCB usage in a CICS region . but after CICS TS V2. This increases the number of processes and might require an increase in the MAXPROCUSER value.3. or later. and receive message: – BPX1040I PROCESS LIMIT MAXPROCUSER HAS REACHED nnn% OF ITS CURRENT CAPACITY OF limtot FOR PID=pid IN JOB name RUNNING IN ADDRESS SPACE asid.BPXI040I messages after upgrading CICS • Problem: You have upgraded from CICS Transaction Server for z/OS (CICS TS) V2. When running under CICS TS V2.2. these were not counted against MAXPROCUSER.
The new command syntax is: – CEDA DIsplay LISt(*) or CEDA DI LIS(*) • The reason for the change was due to the addition of the new CEDA LIBrary command that was added to CICS TS V3. the CEDA command for DISPLAY LIST was changed.CEDA DI LI(*) command does not work in CICS TS V3.2 region for the DISPLAY LIST command. another letter is added to the prefix of each command.2. . • In CICS TS V3. LIST has been assumed. LIST has been assumed.2. • The message displayed on the CEDA panel is: – E 'LI' is ambiguous. When more than one command with the same prefix is added. and you see error message: E 'LI' is ambiguous. but the change was not documented in the CICS Information Center.2 • You enter CEDA DI LI(*) on your CICS Transaction Server for z/OS (CICS TS) V3.
CICS attaches to MQ under the L8 Open TCB. • • • . Getmains fail due to lack of below the line LSQA storage Cause: A large proportion of LSQA storage had been allocated for PRHWs. In CICS releases before CICS TS 3. where CICS has control of MQ-CICS adapter and bridge components. This leads to the possibility of filling LSQA below the line. MQ will getmain PRHW storage from extended LSQA. PRHWs are used by CICS tasks to communicate with MQ through the MQ-CICS adapter. you receive an abend 878 or 80A with reason code x'0C' or x'10'. MQ allocated one PRHW for each of the eight subtask TCBs used for communication between CICS and MQ. program request handler control blocks.878 or 80A abend with reason code x'0C' or x'10' when connected to MQ • Problem: You are running WebSphere MQ for z/OS.2 and above.2. In CICS TS 3. Solution: Apply PTF for MQ V6 APAR PK68189 or MQ V7 APAR PK69439 . Afterwards.2. Because of this there is now no limit to the number of PRHWs that can be allocated. After upgrading to CICS Transaction Server for z/OS (CICS TS) V3.
first clear the CICS screen (clear the screen and erase EOF on the command line). Enter alloc ddname(sysin) dsname(MYFILE. Enter ADYN from a blank CICS screen 2. You specify FREE=CLOSE on each SYSIN DD statement and expect the dataset to be deallocated from CICS once the file is closed. Enter free ddname(sysin) unalloc 3. You are able to successfully deallocate other datasets that specify FREE=CLOSE in the CICS JCL Cause: Your CICS SYSIN input consists of several concatenated PDS datasets. Here is an example of the commands that can be used to deallocate the file "MYFILE. This stops you from being able to delete and reallocate the dataset while CICS is running.SYSIN datasets remain allocated to CICS while CICS is active • Problem: You are unable to deallocate the SYSIN dataset while CICS® is active. z/OS is causing FREE=CLOSE to be ignored due to the dataset being a member of a concatenated group Solution: Use the ADYN transaction to deallocate a file from CICS while CICS is up.CICSTS13. This group contains the transaction definition for ADYN and its associated program. Prior to using ADYN you must install group DFH$UTIL in your CICS region.SYSIN) status(shr) To end ADYN. Then hit enter on the empty screen.CICSTS13.SYSIN" and reallocate it: 1. However. • ADYN is documented to in the CICS TS information center under the dynamic allocation sample program • • . the SYSIN datasets remain allocated to CICS until it is shutdown. Normally the close occurs just after CICS has read the SYSIN parameters during initialization. DFH99.
The first step is to find the modules executing within a CICS region (which will. the message will not be created.3 or lower). therefore. use APARs PK10480 and PK15436.1 will not execute OS/VS COBOL application modules.1 (and any subsequent releases of CICS) will not execute OS/VS COBOL application modules. all OS/VS COBOL modules must be recoded into a supported language (such as Enterprise COBOL).3. Also mentioned in this article: http://www.cfm?section=article&aid=722 . be CICS TS 2. so detection may be incomplete.2 and CICS TS 2. use APAR PK16285. and another within the CICS region. Therefore. install some APARs. However.com/index. There are two approaches. Solution CICS Transaction Server V3.Detection of OS/VS COBOL modules running within CICS Transaction Server Problem How do I find OS/VS COBOL modules running in my CICS® Transaction Server region? Cause CICS Transaction Server V3. For CICS TS 2. Run this with the OSVSONLY option against all load libraries used by CICS to create a listing of the OS/VS COBOL modules. The effect of which will be to create a new message DFHAP1301 when an OS/VS COBOL module is first used within the CICS region. Alternatively.zjournal. in order to prevent application failures within CICS TS 3. This provides an update to the CICS Load Module Scanner.1 region. The best approach is to install SupportPac CH1A.3. One involving batch processing. For CICS TS 1. if an OS/VS COBOL module is not executed.
Each switch is a new dispatch and so the task will have a very high dispatch count and so the USRCPUT time recorded will be significantly less than was actually used. it is possible for the USRCPUT reported for the QUASIRENT case to be less than the USRCPUT reported for the THREADSAFE case. it will have a low dispatch count and so the USRCPUT reported will be very close to the amount used. So for each dispatch of a task. So if a task used 24 microseconds during a dispatch.2 with CICS Precise Monitoring . This effect is sometimes noticed when using CMF data to compare the CPU used by a task when its program is defined THREADSAFE verses when its program is defined QUASIRENT. This can become a significant amount of underreported CPU when a single task has hundreds of thousands of dispatches. CICS will add 16 microseconds to the running USRCPUT total. CICS will under report the CPU used during that dispatch by an average of 8 microseconds. the task will constantly switch from QR to L8 and back. and is defined QUASIRENT. 16 microseconds will be added to the running USRCPUT total. If the CPU used in DB2 and in the application is very small.e. the amount of CPU recorded for a single dispatch of a task is truncated down to the nearest 16 microsecond unit. – If the program makes hundreds of thousands of SQL calls with no interleaving non-threadsafe CICS commands. then 0 will be added to the running USRCPUT. If the task used 31 microseconds or 17 microseconds during a dispatch. the task will not constantly switch. For the CPU time clock fields (i. If the total CPU time was less than 16 microseconds. CICS has always done the CPU reporting this way. USRCPUT). the base unit of time is 16 microseconds.Monitoring CPU Time Higher for True Threadsafe Programs • For CMF (CICS Monitoring Facility) Performance Class data clock fields. • • • But with the same program defined THREADSAFE. – • Note: This is fixed in CICS TS 3.
com/support/docview.com Web site or install on a workstation or server. Here is a link to an item that has all the Information Centers online.ibm. Each release of CICS has its own information center that you can view on the www.wss?rs=1083&context=SSGMGV&uid=swg21200934 • • . Documentation for most of the CICS Tools is also included in the CICS TS information centers. and directions to download to a workstation: – http://www01.Finding CICS Information Centers • How do you find CICS product documentation for CICS Transaction Server for z/OS (CICS TS) and the CICS tools? The best place to find CICS product documentation is to use the CICS TS information centers.ibm.
ts. Order items from the catalog. Inquire on individual items in the catalog.jsp?topic=/com.com/infocenter/cicsts/v3r2/index.html .ibm. Find out more at: – http://publib. in which the end user can perform these functions: – – – List the items in a catalog.doc/sampleapp/topics/dfhxa_t100. • • • The catalog is implemented as a VSAM file.The CICS catalog manager example application • The CICS catalog example application is a working COBOL application that is designed to illustrate best practice when connecting CICS applications to external clients and servers.cics.ibm.boulder.webservic es. The example is constructed around a simple sales catalog and order processing application. The base application has a 3270 user interface. but the application comes with Web service support. which is designed to illustrate how you can extend an existing application into the Web services environment.
Fix lists for CICS TS • Fix list documents summarize all of the APARs and PTFs for a particular product Version • Fixes by version document 7008833 contains a link to the available Fix list documents – Can be linked to from Fixes by version on the CICS Support page • http://www.ibm.com/support/docview.wss?rs=1083&uid=swg27008833 .com/software/htp/cics/tserver/support/ – Direct URL is http://www-1.ibm.
com/software/htp/cics/tserver/support/ – Direct URL is http://www-1.ibm.com/support/docview.wss?rs=1083&uid=swg21231874 .Preventive Service Planning • CICS Document 1231874 has a listing of all PSP buckets for CICS Transaction Server and all CICS Tools – Can be linked to from the CICS Support page • http://www.ibm.
com/support/docview.com/software/htp/cics/tserver/support/ – Direct URL is http://www-1.ibm.wss?rs=1083&uid=swg21238275 .New Function APARs • Flashes for all CICS New Function (NF) APARs are posted to CICS Support page and included in MySupport email • CICS item 1238275 has a listing of links to all New Function APARs for CICS Transaction Server and all CICS Tools – Can be linked to from the CICS Support page • http://www.ibm.
com/software/htp/cics/tserver/support/ – Direct URL is: http://www-1.ibm.com/support/docview.wss?rs=1083&uid=swg21227090 .Announcement Letters for CICS • CICS item 1227090 contains links to all Announcement letters for CICS Transaction Server and all CICS Tools • Can be linked to from Announcement Letters on the CICS Support page – http://www.ibm.
2 5655-M15 25 Jan 2002 19 Dec 2003 25 Mar 2005 29 Jun 2007 30 Apr 2008 30 Sep 2009 .3 5697-E93 CICS Transaction Server for z/OS V3. You can find the End of Service dates by navigating to the following URL: http://www.ibm.1 5655-M15 CICS Transaction Server for z/OS V3.IBM Software Support Lifecycle You want to know when the end of service is for any IBM Software release.html CICS Transaction Server for z/OS V2.com/software/info/supportlifecycle/list/c.2 5697-E93 CICS Transaction Server for z/OS V2.
and cumulative maintenance for CICS or any of the CICS tools See the following document for all product or maintenance ordering concerns http://www-1.wss?fdoc=aimcics&rs=1083&context=SSGMGV&uid=swg21049360 . individual PTFs.ibm. You want to know what options are available for ordering the product.Order processing for CICS products and maintenance You would like to order a CICS® product or maintenance.com/support/docview.
helps IBM® Support quickly determine if: 1. Collecting MustGather data early. 2.ibm. Locating root cause can speed development of a code fix. 3. There is a defect that identifies a workaround to reduce severity. These documents are located on the CICS® Web site and contain instructions about what documentation to gather for specific problems. Symptoms match known problems (rediscovery). even before opening a PMR.Must Gather Documentation MustGather documents aid in problem determination and save time resolving problem management records (PMRs). You can find the MustGather – Read first document on the CICS Home Page or go directly to: http://www-1. There is a non-defect problem that can be identified and resolved.wss?rs=1083&uid=swg21208053 . 4.com/support/docview.
ibm.com/software/htp/cics/support/ .PE and HIPER APARs • CICS DCF item 1182322 will dynamically show all PE and HIPER maintenance for all supported releases of CICS and CPSM • You can find this item by going directly to: • http://www-1.com/support/docview.ibm.wss?rs=166&context=SSGMGV&uid=swg21182322 • Note: CICS Home Page: http://www.
com/support/docview. • You can find this item by going directly to: • http://www-1.wss?rs=166&context=SSGMGV&uid=swg21207399 • Note: CICS Home Page: http://www.Migration information for CICS when changing release or operating system • CICS Document 1207399 may be used to see if there are Migration Issues with CICS and CPSM.ibm.com/software/htp/cics/support/ .ibm.
com/support/docview.ibm.wss?rs=1083&context=SSGMGV&uid=swg21176381 . you would like to locate the PSW and registers in your CICS system dump. Since the X'FFFF' indicates that CICS® was unable establish the location of the program check. DFHAP0001 An abend (code 0C4/AKEA) has occurred at offset X'FFFF' in module DFHAPDM. • Solution: Review the following CICS Document for debugging information: http://www-1.Locating the PSW for a program check in a CICS system dump • Problem: You receive a program check that has an offset of X'FFFF'. For example.
CICS support news is now available on Twitter • CICS Transaction Server (CICS TS). updates. and CICS Transaction Gateway (CICS TG) support news is now available on Twitter.wss?rs=1083&context=SSGMGV&uid=swg21384915 . • Here is a link with more information: – http://www01.ibm.com/support/docview. You can follow IBM_CICS on Twitter to find news. and other information for the CICS products. CICS Tools.
wss?uid=swg21422149 Follow IBM_CICS support news on Twitter: http://www.com/support/docview.wss?uid=swg21384915 Sign up to receive technical support e-mails: http://www.ibm.html CICS Featured documents: http://www.ibm.ibm.ibm.wss?uid=swg27007244 CICS Transaction Server Support Web page: http://www.com/support/entry/portal/Overview/Software/Other_Software/ CICS_Transaction_Server • • • • • .com/software/support/einfo.ibm.ibm.com/support/docview.Additional Product Resources • Tracking specific CICS APARs or CICS APARs by component id: http://www.com/support/docview.wss?uid=swg27006900 Webcasts for CICS and OMEGAMON: http://www.com/support/docview.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.