NOMAD Version 6.52 SCHEMGEN Enhancements


Default DATE Display Formats Can Be Specified With Four-Digit Years

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.

/*
/*
/*
/*
/*
/*
/*
/*
/*
/*
/*
/*
/*
/*
/*
/*
/*
/*
/*
/*
/*
/*
/*
/*
/*
/*
/*
-----------------------------------------------------------------

Date/Time Column Display Format:
The following &variables control the default display formats for
Date and Time data types. These display formats must be enclosed
in single quotes, thus the repeated single quotes below. These
values are used as follows:

 
  Variable
--------
&SQ_DATE
&SQ_TIME
&SQ_DATETIME
SQL & DB2
----------
DATE
TIME
TIMESTAMP
Teradata
---------
DA
 
The default display formats are:
  &SQ_TIME = 'TIME''HH:MN:SS''' ;
&SQ_DATE = 'DATE''' cat (if query(dateorder) eq 'MD'
    then 'MM/DD' else 'DD/MM') cat '/YY''' ;
  &SQ_DATETIME = 'DATETIME''' cat (if query(dateorder) eq 'MD'
    then 'MM/DD' else 'DD/MM') cat '/YY HH:MN:SS''' ;
Four-digit years require that you change the literal "/YY" to
"/YYYY" in the assignments to &SQ_DATE and &SQ_DATETIME. (This
might be required at some sites for Year 2000 compliance.)
----------------------------------------------------------------
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/

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:

&SQ_DATE = 'DATE''' cat (if query(dateorder) eq 'MD'
  then 'MM/DD' else 'DD/MM') cat '/YYYY''' ;
&SQ_DATETIME = 'DATETIME''' cat (if query(dateorder) eq 'MD'
  then 'MM/DD' else 'DD/MM') cat '/YYYY HH:MN:SS''' ;

Table of Contents 23


NOMAD Version 6.52 NOMAD Error Messages

RP/Server using TCP/IP Communications

NOMAD Error Messages

The following error messages have been added to NOMAD since Version 6.50.

1677 Messages from JOB "dropped due to out-of-sequence condition.
MVS shared database error. And unexpected message was received from the named JOB/USERID. The message is not the correct format for a first communication, but the sender is unknown to the server.
This message is usually preceded by message 1638.
1768 ABEND "during OPEN of DDNAME".
An ABEND has occurred during OPEN of named data set. Processing requiring the data set cannot continue. This is most likely to be caused by insufficient below-the-line storage. Increasing the region size may prevent this error
1810 Trace Y2K has been disabled.
The TRACE Y2K option has been turned off. This is probably due to insufficient resources, such as memory, for trace file processing.
1946 "may not both be specified at this time
FILE DEFINE/OPEN ... XCF has been used. There are two ways to specify several of the parameters. Both have been used, but only one is valid. (RP/Web only)
1947 /"/ is invalid XCF token for".
FILE DEFINE/OPEN ... XCF has been used. If a token is used then it must be a specific length and only contain valid hex. (RP/Web only)
1948 No IUCV connection could be created for ". RC was "from".
FILE DEFINE/OPEN ... IUCV has been used. While attempting to create the connection, a non-zero return code was received. (RP/Web only)
1949 SENDFIRST was specified or implied for ". No ID to connect with was specified.
FILE DEFINE/OPEN ... IUCV has been used. SENDFIRST was specified. However, the SESSIONID was not specified. (RP/Web only)
1950 IUCV error "for fileid".
FILE DEFINE/OPEN ... IUCV has been used. Read or write was attempted, and an IUCV error resulted. The IUCV error code is given. (RP/Web only)
1951 XCF "failed for ddname: "-"
the indicated XCF funtion (OPEN, CLOSE, READ, or WRITE) has failed. The error message returned from the XCF interface is shown and indicates the reason for the failure. (RP/Web only)
1952 N2TERA - data mismatch for VIEW.
NOMAD has received the DATAINFO parcel from Teradata. NOMAD thinks it has packed data, but the DATAINFO indicates it is not.

The text of the following error message has been changed in Version 6.52.

1952 To load data, invoke macro".
this message appears in a 1-2-3 worksheet when a CREATE...FOR LOTUS 123 WKS file is retrieved into the 1-2-3 environment and &WKSMACRO has a value other than "/0". The message tells the user to execute a macro defined in a TXT file, which loads detail data and sets column formats. (When the macro name is "/0", the default macro name, then macro defined in the TXT file is automatically executed without intervention by the user when the WKS file is retrieved.)
Table of Contents 24


Behavior Changes in NOMAD 6.50 NOMAD Error Messages

Behavior Changes in NOMAD 6.52
  • The following behavior changes occurred in NOMAD Version 6.50, but were not documented.


DDQUERY Function - Extra Blanks in Parameters

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:

print ddquery('type','stars.star_code');

The following command is not valid:

print ddquery('type','stars .star_code');


LIST Command - BYFOOT with TAB

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:

LIST ...
BYFOOT xitem TAB n DASHES... TAB n DASHES
  ' TOTAL ' &xitem DOSUBTOT ...
Table of Contents 25


Documentation Clarifications NOMAD Error Messages
Behavior Changes in NOMAD 6.50


&SYSRC When Exiting NOMAD

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.

OPTION EXITPROC Called Procedure Exit Procedure &SYSRC
off (not set) no error   Current &SYSRC value
error   Return code from the called procedure
ON no error no error Current &SYSRC value
error no error Return code from the called procedure
no error error Return code from the exit procedure
error error Return code from the exit procedure

For more information on the OPTION EXITPROC command, refer to the NOMAD Reference Manual.


VM Shared File System (SFS) - Warning

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


DEFINE Statement - SDATE Parameter

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.


ITEM Statement - SDATE Parameter

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.


DATE Display Format With OPTION LANGUAGE FRENCH/CFRENCH

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.

option language cfrench;
declare &x as date;
&x= '2 FEVRIER 98';
print &x as date'Month Dom, YYYY';
print &x as date'Le Dom de Mon, YYYY';

&X=FŽvrier Second, 1998
&X=Le Second de FŽv, 1998


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.


WINDOW CREATE Command- Textual Windows Maximum Value

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.

WINDOW CREATE window-name
LINESIZE n
COLSIZE n
[BUFFER NONE];

Required Parameters

window-name

The name of the window to be created, which is limited to 8 bytes in length. For more information on window-names, refer to the earlier section "WINDOW Commands - General Syntax."

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]


MASTER Statement - Length of Master Name

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.


TEXT Display Format - Maximum Display Width

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.

... variable AS TEXT ['30/n]
  [I=B,3/n1,0/n2]
  [JU=YES/NO]']

... variable AS TEXT['[30/n] [ASIS]']

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.


SCHEMGEN/TQLGEN Databases for Teradata

The following chart shows which SCHEMGEN databases are valid with different versions of Teradata.

SCHEMA Mainframe Teradata Version UNIX Teradata Version
SCTQL410 4.1 and later  
SCTQL420 5.0 and later 2.0 and later
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.