For SYSTEM 2000 Version: 1.0
Problem Status: ZD -- V1 FFD1
Description of Problem:
S0C4 ABEND AFTER S2KDIAG LOGLEVEL INCREASED TO ADD TSPIO. UPDATING A DATABASE AFTER TURNING ON TSPIO MAY RESULT IN S0C4.
Note: Please send email to s2k@sas.com telling us which problem fixes you have downloaded so we can keep track of the fixes at your site in case questions or problems arise.
Top of Zap Deck:
* IBM V1.0 BUG 4965 OS ************************************************************ * SYMPTOM: * A 0C4 OCCURRED AFTER A LOGLEVEL CHANGE TO TURN ON TSPIO. * ROUTINES THAT ACCESS DECB FIELDS MIGHT GET A S0C4 BECAUSE * VSAMIO DID NOT FILL OUT DUE TO TSPIO SWITCH NOT SET CORRECTLY. * * PROBLEM: * VSAMIO DOES NOT CHECK LOGLEVEL TSPIO AFTER FIRST TIME THRU. * IF TSPIO IS MODIFIED BY OPERATOR COMMAND IT MIGHT BE INVALID. * * SOLUTION: * FORCE VSAMIO TO CHECK TSPIO EVERYTIME THRU. * ************************************************************ NAME SYS2K VSAMIO VER 0122 95FF,C384,4770,C15E REP 0122 0700,0700,0700,0700 CHECKSUM 9404EC91
End of Zap Deck