NOMAD Version 6.52 | SCHEMGEN Enhancements | ||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||
To allow easy adjustment for Year 2000 compliance, an additional section has been added to the SGENPRFE NOMAD procedure. SGENPRFE contains a detailed description of each of the &variables that can be included in SGENPROF in order to customize SCHEMGEN. SGENPRFE NOMAD contains a detailed description of the &variables in SGENPROF NOMAD; actual customizing of SCHEMGEN is accomplished by altering SGENPROF NOMAD. Following is the new section of SGENPRFE NOMAD that deals with DATE display formats. |
|||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||
This shows the default display formats assigned to date items by SCHEMGEN currently. The &variables &SQ_DATE and &SQ_DATETIME can be copied to SGENPROF NOMAD with their display formats modified to YYYY. Once this has been done, the year values of dates will display with four digits automatically. Although this feature was designed with Year 2000 compliance in mind, it can be used to customize the default DATE display format assigned to date fields by SCHEMGEN at your site. The specific display format for any item can still be overridden on a per-item basis using existing facilities. The following &variables, in SGENPROF NOMAD, have been modified to display four-digit years:
|
|||||||||||||||||||||||||||||||||||||||||
Table of Contents | 23 |
NOMAD Version 6.52 | NOMAD Error Messages | ||||||||||||||||||||||
RP/Server using TCP/IP Communications The following error messages have been added to NOMAD since Version 6.50. |
|||||||||||||||||||||||
The text of the following error message has been changed in Version 6.52.
|
|||||||||||||||||||||||
Table of Contents | 24 |
Behavior Changes in NOMAD 6.50 | NOMAD Error Messages | ||||||
|
|||||||
Behavior Changes in NOMAD 6.52 | |||||||
|
|||||||
When using dot notation to qualify an entity used with the DDQUERY function, DDQUERY does not accept spaces preceding the dot. The following command is valid:
The following command is not valid:
|
|||||||
In versions of NOMAD prior to 6.50, a LIST command with BYFOOT and TAB that produced lines longer than 131 characters, did not spill to a new physical page (Page 1.1). Instead, the output wrapped to the beginning of the same physical line. In Version 6.50 and later, this same request spills to a new physical page. The following is an example of the LIST command. Note that TAB n DASHES is repeated enough times to extend the line beyond column 131:
|
|||||||
Table of Contents | 25 |
Documentation Clarifications | NOMAD Error Messages | ||||||||||||||||||||||||
Behavior Changes in NOMAD 6.50 | |||||||||||||||||||||||||
The following chart shows the value of &SYSRC when a syntax error or an execution error occurs in either a called NOMAD procedure or in the exit procedure. The value of &SYSRC is passed to the operating system upon exit from NOMAD. |
|||||||||||||||||||||||||
|
|||||||||||||||||||||||||
For more information on the OPTION EXITPROC command, refer to the NOMAD Reference Manual. |
|||||||||||||||||||||||||
Prior to CMS 10, changes made to an SFS file during a NOMAD session, such as with the SYSTEM EDIT command, would not be committed until the NOMAD session ended. This has been corrected in CMS 10. Therefore, the use of SFS files by NOMAD when running in versions of CMS prior to Version 10 is limited to SFS files created outside of the NOMAD environment. To access SFS files, you must define the file to NOMAD using the FILEMODE parameter of the FILE command. |
|||||||||||||||||||||||||
Table of Contents | 26 |
Documentation Clarifications | NOMAD Error Messages |
The SDATE parameter of the DEFINE statement specifies the DATE value for the first subscript of a time-series array. The display format of SDATE is DATE if the periodicity of the array is MONTHLY or larger. The display format of SDATE is DATETIME if the periodicity of the array is HOURLY or smaller. |
|
The SDATE parameter of the ITEM statement specifies the DATE value for the first subscript of a time-series array. The display format of SDATE is DATE if the periodicity of the array is MONTHLY or larger. The display format of SDATE is DATETIME if the periodicity of the array is HOURLY or smaller. |
|
The following example shows the results of printing a date when using OPTION LANGUAGE FRENCH or OPTION LANGUAGE CFRENCH. This is a correction to the example on page 6 of the NOMAD Documentation Updates Version 6.50. The example used the word Deuxime instead of Second.
|
|
FILE OPEN Command - LENGTH Parameter The following text should replace the section "Specifying Record Length" on page 9-12 in the NOMAD Reference Manual. Specifying Record Length If LENGTH is not specified when a file is opened for output, the default record length is 80 bytes. If LENGTH is not specified when a file is opened for input, the default record length is the LRECL of the file or data set. The input LRECL cannot be overridden. Specifying a different LENGTH parameter may cause the open to fail with a FIL1602 (or other) error message, or may cause an abend. The input BLOCKSIZE can be overridden, provided the specified size is larger than the actual BLKSIZE of the file or data set, and the specified size is a multiple of the LRECL of the file or data set. |
|
The following text replaces that found in Chapter 11 of the NOMAD Reference Manual. This clarifies the upper size limit of the COLSIZE parameter used in the WINDOW CREATE command. |
|
Table of Contents | 27 |
Documentation Clarifications | NOMAD Error Messages | |||||||||
The WINDOW CREATE command defines textual windows. Textual windows allow you to view the output of a LIST, PRINT, WRITE, or SLIST through a window. |
||||||||||
|
||||||||||
Required Parameters window-name |
||||||||||
|
||||||||||
LINESIZE n | ||||||||||
Specifies the number of lines in the textual window. |
||||||||||
COLSIZE n | ||||||||||
Specifies the column width of the textual window. Textual windows have a COLSIZE upper limit of 1024. |
||||||||||
Optional Parameters [no changes] |
||||||||||
The following text replaces that used in Chapter 6 of the NOMAD Reference Manual. This entry explains that the rules for a valid master-name parameter of the MASTER statement may differ from those described for a native NOMAD master when the DB2 Interface or the SQL Interface is being used. master-name |
||||||||||
Specifies the name of a master. The master name can be up to 15 characters long, beginning with a letter, and can consist of any of the characters A - Z, 0 - 9, and the underscore. For native NOMAD masters, the first seven characters must be unique within the schema, as well as any other active databases, unless you specify the FILETYPE parameter to assign a unique file type explicitly to the master. When the MASTER statement is being used to map a NOMAD schema to a DB2 or SQL table, refer to the Users Guide that applies to the Interface for details on acceptable master-name values with that Interface. |
||||||||||
The following text replaces that used in Chapter 3 of the NOMAD Reference Manual. It points out the maximum width that can be specified for the display of a textual item is 256. |
||||||||||
|
||||||||||
Required Parameters [no change] Optional Parameters 30/n |
||||||||||
Specifies the width to be used when displaying the text. The default is 30 character spaces. The maximum width that may be specified is 256 characters. |
||||||||||
The following chart shows which SCHEMGEN databases are valid with different versions of Teradata. |
||||||||||
|
||||||||||
Table of Contents | 28 |
copyright
The Boeing Company, 1997, 1998, 1999, 200, 2001 No part may be printed, reproduced or distributed without prior written permission Used here with permission of The Boeing Company Line Management, Customer Relations, Ethics, Legal and Copyright Offices |
All
images on this site ©1996-2001, Judy Tallant, All Rights Reserved,
except where noted. Permission must be obtained for use of any image contained herein for any purpose.
|