PILOT Fixes
back to support by product page

The following fixes are available for PILOT.

Version 1.7.0

PIL17001: The PILOT/SMF Control Card Scanner does not properly recognize four digit years in the Gregorian format. Data selection fails with no records extracted, as the test values used for the start and end dates are not the dates you specified on your READSMF control cards. Symptoms: Messages PILOT209E, PILOT002I and PILOT003I are issued and no data it is selected even though the input contains data that meets the START= and END= parameter conditions.

PIL17002: The PILOT/SMF Authorized Task processor exits 31 bit mode too early in its processing. If it is processing the SMF control block (that defines a MANx data set) which it is above the line, the data area it is referenced in 24 bit mode and can result in incorrect processing or an abend S0C4. Symptoms: Abend S0C4 in module RDSMFAUT at offset X'015A'. Registers 3 and 4 will contain a 31 bit address.

PIL17003: The operator console message PILOT010, issued to request permission to clear the MANx data set being dumped, does not list the full data set name if the data set name exceeds 9 characters, and the data set name displayed it is always of the format SYS1.MANx where x it is taken from the 9th position of the actual data set name. Symptoms: Message PILOT010 displays an incomplete and/or incorrect data set name.

PIL17004: The use of the HISTORY file to locate and process SMF data previously dumped, does not support the selection of data from more than one member or the concatenation of multiple input data sets as input to the process. Symptoms: Data selected will come from only one member, the first member for which the selection criteria specified apply.

PIL17005: The sample member SMFDUMP specifies an output data set block size parameter of 32767, which it is invalid for VB or VBS output. The largest permitted value it is 32760 if unblocked, and 32756 if the data set it is blocked. Symptoms: If used without modification, the supplied block size will result in a JCL error.

PIL17006: The PILOT/SMF Exception Record processor was not updated when the record count was changed from a 4 byte packed field to a 4 byte binary field to allow for larger input files. Symptoms: Abend S0C7 in module RDSMFXCP at offset X'01FE'.

PIL17007: The PILOT/SMF ESTAE Recovery processor was not updated when the record count was changed from a 4 byte packed field to a 4 byte binary field to allow for larger input files. Symptoms: Incorrect output in the WTO message issued by RDSMFRCV with the "RDSMF?ESTAE RECORDS READ=xxxxxxx,BLOCK COUNT=nnnnnnn" where xxxxxxx it is not a numeric string.

PIL17008: The PILOT/MVS Record Type 72 processor attempts to access a date field (4 byte packed) with the wrong base address. The Simulation Builder program module SIM72 has the same problem. Symptoms: RDSMFRMF abends with abend code S0C7 at offset X'45A' in module RMF72 in load module SMFPC (RDSMFRMF). SIMBUILD abends with abend code S0C7 at offset X'45A' in module SIM72 in load module SIMBUILD.

PIL17009: The GENMONTH program incorrectly sets the last day of the month to 31 for all months starting with April. Symptoms: The ending date in the NXTMONTH member it is always mm/31/yyyy for all cases where mm it is 04 or larger.

 

home | products | about Axios | support | contact us