|
|
| Line 1: |
Line 1: |
|
| | #REDIRECT [[New and updated messages in Model 204 version 7.8 (Beta)]] |
| [[Release notes for Model 204 version 7.8|Back to release notes]]
| |
|
| |
| <div class="noautonum">__TOC__</div>
| |
| This topic lists messages that were added or changed for Model 204 version 7.8.
| |
|
| |
| <p style="color:red"><b>******THIS IS A DRAFT DOCUMENT.******</b></p>
| |
|
| |
| ==M204 messages==
| |
| ===<b id="M204.0141:"></b>M204.0141: Bug .. duplicate file name in checkpoint record===
| |
| <P>
| |
| A duplicate file name was encountered while attempting to add a deferred update data set to the file directory during recovery. This indicates a potential bug in the Model 204 software. </P>
| |
| <p>
| |
| <b>System manager response:</b> Contact [[Contacting Rocket Software Technical Support|Technical Support]] with the following documentation: </p>
| |
| <ul>
| |
| <li>Audit trail from the previous run </li>
| |
| <li>Journal from the previous run </li>
| |
| </ul>
| |
| <p>
| |
| <b>Operator response:</b> Notify the system manager. </p>
| |
| {{Template:M204.0141 footer}}
| |
| | |
| ===<b id="M204.0143:"></b>M204.0143: No files changed after last checkpoint, RESTART bypassed===
| |
| <P>This message indicates that no updates were detected while scanning the checkpoint data set beyond the last checkpoint or the specified checkpoint. </P>
| |
| {{Template:M204.0143 footer}}
| |
| | |
| ===<b id="M204.0165:"></b>M204.0165: Missing an update unit from ICL (InComplete List)===
| |
| <P>
| |
| While scanning the CCARF data set, Model 204 has detected the end of an update unit for which no corresponding start of update unit was found. Possible explanations for this error are: </P>
| |
| <ul>
| |
| <li>A utility program was used to copy the original journal to data set being used as CCARF, and a portion of the original data set was not copied. </li>
| |
| <li>A copy was not done. </li>
| |
| </ul>
| |
| <p>
| |
| <b>System manager response:</b> If the original journal was a multi-volume data set and was copied to another data set for input to this run, verify that all volumes were in fact copied, and rerun the job. If CCARF was the original data set, contact [[Contacting Rocket Software Technical Support|Technical Support]]. Have the following documentation available: </p>
| |
| <ul>
| |
| <li>Audit trail of the original run </li>
| |
| <li>Snap </li>
| |
| <li>UTILJ of the CCARF data set or a copy of this data set on tape </li>
| |
| <li>UTILC of the restart data set or a copy of this data set on tape </li>
| |
| </ul>
| |
| {{Template:M204.0165 footer}}
| |
| | |
| ===<b id="M204.0352:"></b>M204.0352: IODEV=nn, Ok uuuuuuuuuu aaaaaaaaaa llllll yy.ddd mmm dd hh.mm.ss ccc nnnnnnnn===
| |
| | |
| The layout of this message has been reformatted to accommodate five digit user numbers.
| |
| | |
| {{Template:M204.0352 footer}}
| |
| | |
| ===<b id="M204.0479:"></b>M204.0479: process group not found: <i>processgroupname</i>===
| |
|
| |
| A <var>[[Statement syntax#TRANSFER|TRANSFER]]</var> statement was evaluated, resulting in an attempt to perform a VTAM trusted logon in another Online (the target Online). The <var>PARTNER</var> processgroup, identified in the <var>[[DEFINE PROCESS command: Transfer Control partner|DEFINE PROCESS]]</var> command in the transferring Online, was not found in the target Online. As a result, the TRANSFER fails and the user remains in the transferring online.
| |
|
| |
| <b>System manager response:</b> The <code>PARTNER=</code> token in the <var>DEFINE PROCESS</var> command of the transferring Online has an incorrect value for <var class="term">processgroupName</var>. Check the spelling to ensure that it is the correct name of the intended processgroup in the target Online.
| |
|
| |
| <b>Return codes:</b> I 0 0 AUDITMS
| |
| ----
| |
|
| |
| ===<b id="M204.0480:"></b>M204.0480: Invalid backpage request: backPage===
| |
| <p>
| |
| A backpage command of the form <var>P -<i>n</i></var> or <var>P +<i>n</i></var> was issued, but <var>[[NBKPG parameter|NBKPG]]</var> is 0, or the value of <var class="term">n</var> is invalid. The command is echoed in hex, so you can see exactly what was entered. For example, if <code>P -99</code> was issued but <var>NBKPG</var> is 50, then the following message would be issued:</p>
| |
| <p class="code">M204.0480: Invalid backpage request: P -99(X'D74060F9F9')</p>
| |
| <p>
| |
| <b>Response:</b> Correct the backpage command, or set <var>NBKPG</var> greater than 0.
| |
| </p>
| |
| {{Template:M204.0480 footer}}
| |
| | |
| ===<b id="M204.0481:"></b>M204.0481: Procedure procName in subsysName could not be made resident; increase RESPAGE or RESSIZE ===
| |
| <p>
| |
| The named procedure in the named subsystem could not be made resident in resident request storage.
| |
| </p>
| |
| <p>
| |
| <b>Response:</b> Increase the size of resident request storage with a <var>[[RESSIZE parameter|RESSIZE]]</var> or <var>[[RESPAGE parameter|RESPAGE]]</var> parameter in CCAIN. <var>RESSIZE</var> (below-the-bar storage) can be dynamically reset, but <var>RESPAGE</var> (above-the-bar storage) cannot.
| |
| </p>
| |
| {{Template:M204.0481 footer}}
| |
| | |
| ===<b id="M204.0541:Procedure"></b>M204.0541:Procedure is in use: procedure===
| |
| <P>The procedure named in the message is currently in use by another user. The command entered cannot be processed until the procedure is no longer in use. </P>
| |
| <p><b>Response:</b> Retry the command when the procedure is no longer in use. </p>
| |
| {{Template:M204.0541 footer}}
| |
|
| |
| ===<b id="M204.0569:"></b>M204.0569: File filename?,? Find: Table B records to be searched ?=? number===
| |
| The message test now includes the filename, to help track down the cause of the direct search. This change has been enabled within v7.7 with the application of zap 77z032, and within V7.6 with the application of zap 76z386.
| |
| {{Template:M204.0569 footer}}
| |
|
| |
| ===<b id="M204.1070:"></b>M204.1070: ALLOCATE ddName failed - reason===
| |
| This message has been changed to add the ddname of the failing dataset to the message text.
| |
| {{Template:M204.1070 footer}}
| |
| | |
| ===<b id="M204.1500:"></b>M204.1500: <i>token</i> ===
| |
| <p>Message M204.1500: <var class="term">token</var> has a new form relevant to the [https://m204wiki.rocketsoftware.com/index.php/CA-ACF2_MVS_interface CA-ACF2 MVS], [https://m204wiki.rocketsoftware.com/index.php/CA-ACF2_VM_interface CA-ACF2 VM], [https://m204wiki.rocketsoftware.com/index.php/Security_Server_(formerly_RACF)_interface Security Server (formerly RACF)], and [https://m204wiki.rocketsoftware.com/index.php/CA-Top_Secret_interface CA-Top Secret] Model 204 security interfaces.</p>
| |
|
| |
| <p>When the default user fails to log in, the security interface is operational but CCASTAT logons are not allowed. The following error message is displayed:</p>
| |
| <p class="syntax">M204.1500: CCASTAT logons not allowed</p>
| |
| {{Template:M204.1500 footer}}
| |
| <!-- skeleton as it was in pdf/message number message text /-->
| |
| ----
| |
| | |
| ===<b id="M204.1899"></b>M204.1899 Transfer statement from sourceVtamName to targetVtamName complete, User userId disconnected===
| |
| The message, issued when a VTAM Transfer statement completes, now contains the source and target VTAM names for the transfer process.
| |
| | |
| The change in message text is enabled within V7.7 with the application of zap 77z310.
| |
| {{Template:M204.1899 footer}}
| |
| | |
| ===<b id="M204.1900"></b>M204.1900 User userId transferred to targetVtamName from sourceVtamName===
| |
| This message, issued on the target ONLINE when a user has transferred to that ONLINE, now displays the source and target VTAM names involved in the VTAM Transfer.
| |
| | |
| The change in message text is enabled within V7.7 with the application of zap 77z310.
| |
| {{Template:M204.1900 footer}}
| |
| | |
| ===<b id="M204.2020"></b>M204.2020 File fileName; condition?,? OPEN command rejected===
| |
| The first change to this message is that the filename of the affected file is now displayed at the beginning of the message text.
| |
|
| |
| The second change is that a second error type affecting file opens is now support. The original error type of "Unsupported device for Model 204 database %F" was reported for all condition,s even where the device type wasn't the underlying issue. Whilst this error type has been retained for conditions where it is valid, a new error type of "DDNAME not found" is now available for the message. Thus, in a situation where one thread is attempting to allocate a ddname, and another thread in parallel is trying to open a file with the same ddname, the following message variant may be produced
| |
|
| |
| M204.2020: File filename; DDNAME not found, OPEN command rejected
| |
|
| |
| {{Template:M204.2020 footer}}
| |
|
| |
| ===<b id="M204.2700"></b>M204.2700 CHECKPOINT command ignored: sub-transaction checkpoint in progress===
| |
| <P>
| |
| A <code>[[CHECKPOINT_command|CHECKPOINT]] (TRAN | SUBTRAN | ABORT)</code> command was issued while the system was taking a sub-transaction checkpoint. The command is ignored. If this message was issued in response to a <code>CHECKPOINT ABORT</code> command, the
| |
| sub-transaction in progress has passed that phase of its processing during which it can be aborted.
| |
| </P>
| |
| {{Template:M204.2700 footer}}
| |
| | |
| ===<b id="M204.2964"></b>M204.2964 Password missing or too long===
| |
| <p>
| |
| A password string within an IFSTRTN call has not been delimited with a semicolon.
| |
| </p>
| |
| <p>
| |
| <b>Response:</b>
| |
| Ensure that the password string is delimited by a semicolon, as in the following example
| |
| </p>
| |
| <p class="code>CALL IFSTRTN(RC,'logonid;password;'...)</p>
| |
| <p><b>Version introduced:</b>
| |
| 7.8 | |
| </p>
| |
| <b>Return codes:</b> E 00 04 AUDITMS NOCOUNT
| |
|
| |
| ===<b id="M204.2965"></b>M204.2965 Unable to cleanly close log file(s)===
| |
| <p>Introduced in zap 77z243.</p>
| |
| <p>This message causes a snap/dump if the log file (such as a journal, jlog, or checkpoint) cannot be cleanly quiesced when bringing down an Online. The problem with the log file is rare but caused a hang further along in processing. This message causes a snap/dump much closer to the time of error, making it easier to diagnose the problem.</p>
| |
| <p><b>Response:</b> Use the snap/dump generated by the message to diagnose the cause of the error.</p>
| |
| <b>Return codes:</b> E 88 88 DUMP SNAP AUDITAD NOTERM OPR
| |
| ----
| |
|
| |
| ===<b id="M204.2966"></b>M204.2966 <i>what</i> line <i>number?</i>,? procedure <i>proc</i> in file <i>file</i>===
| |
| <p>
| |
| This message provides diagnostic information following various types of error messages. </p>
| |
| <p>
| |
| The first M204.2966 message after an error has <var class="term">what</var> set to <code>Error at</code>. Subsequent M204.2966 messages (if any) have <var class="term">what</var> set to <code>Called from</code>. </p>
| |
| <p>
| |
| <var class="term">number</var>, <var class="term">proc</var>, and <var class="term">file</var> indicate the line number, procedure, and file where the error occurred or from where the previous M204.2966 entry was called. Essentially, this provides a call stack trace to aid in diagnosing problems. No more than 20 levels of calls are shown for an error. </p>
| |
| <p>
| |
| <b>Response:</b> Use the M204.2966 messages after an error to try to diagnose the cause of the error.
| |
| </p>
| |
| {{Template:M204.2966 footer}}
| |
| ----
| |
| ===<b id="M204.2967"></b>M204.2967 <i>what</i> line <i>number</i> of command level program===
| |
| <p>
| |
| This message provides diagnostic information after various types of error messages. </p>
| |
| <p>
| |
| The first M204.2967 message after an error has <var class="term">what</var> set to <code>Error at</code> and subsequent M204.2967 messages (if any) have <var class="term">what</var> set to <code>Called from</code>. </p>
| |
| <p>
| |
| <var class="term">number</var> indicates the line number for a command line program (counting from the <var>Begin</var>) where the error occurred, or where the previous [[M204.2966]] entry was called from. Essentially, this provides a call stack trace to aid in diagnosing problems. No more than 20 levels of calls are shown for an error. </p>
| |
| <p>
| |
| <b>Response:</b> Use the M204.2967 (and M204.2966, if any) after an error to try to diagnose the cause of the error.
| |
| </p>
| |
| {{Template:M204.2967 footer}}
| |
| ----
| |
| ===<b id="M204.2968"></b>M204.2968 <i>what</i>: no debug info===
| |
| <p>
| |
| An error message (immediately preceding M204.2968) was issued, but insufficient compile-time information was collected to provide the diagnostic information provided in the [[M204.2966]] and [[M204.2967]] messages.
| |
| To get that additional information to help diagnose the problem, set the [[SIRFACT parameter|SIRFCAT X'01']] bit if authorized for [[SirFact]], or set the [[DEBUGUL parameter]] to a non-zero value. The latter requires no product authorization, but it does increase QTBL requirements. </p>
| |
| <p>
| |
| <b>Response:</b> If you are unable to diagnose the problem, consider setting one of the parameters described above to aid in problem diagnosis.
| |
| </p>
| |
| {{Template:M204.2968 footer}}
| |
| ----
| |
| ===<b id="M204.2969"></b>M204.2969 MBSCAN (<i>mbscan</i>) exceeded?,? records to be searched ?=? <i>number</i>===
| |
| <p>
| |
| A Table B scan would exceed the setting of <var>[[MBSCAN parameter|MBSCAN]]</var>, so the request is cancelled. </p>
| |
| <p>
| |
| <b>Response:</b> Correct the <var>Find</var> statement at the line indicated by the following [[M204.2966]] message (hopefully available), or increase <var>MBSCAN</var> to tolerate the number of scanned records, if reasonable.
| |
| </p>
| |
| {{Template:M204.2969 footer}}
| |
| ----
| |
| ===<b id="M204.2970"></b>M204.2970 Maximum call stack limit (<i>limit</i>) reached===
| |
| <p>
| |
| The number of messages describing the call stack reached the maximum allowed for such messages (currently 20). This message is largely informational; it is more useful to focus on the preceding [[M204.2966]] messages. </p>
| |
| <p>
| |
| <b>Response:</b> Examine the preceding M204.2966 messages.
| |
| </p>
| |
| {{Template:M204.2970 footer}}
| |
| ==MSIR messages==
| |
| ===<b id="MSIR.0942"></b>MSIR.0942 Debugger token0 port defaulted to token2===
| |
| This message has been changed from an error message to an informational message
| |
| {{Template:MSIR.0942 footer}}
| |