• Date Display Edits

    When working with DATE type fields, the EDIT code is not used to format the date value displayed.  Edit codes are only used for numeric type fields.  Try changing the view properties for DATE STYLE and select *USA to display date fields with slash separators.

    Originally Posted By richg

  • RUNSCRIPT command

    Usa the RUNSCRIPT or BCHSCRIPT command to run SEQUEL scripts.  Prompt the command at a command line to see avaialable parameters. 

    Originally Posted By richg

  • What Windows OS and MS Office

    What Windows OS and MS Office versions are you using?  If WIn-7 or Office 10, you need to update the ViewPoint client to make it compatible with the MS products.  Download the ViewPoint update from this website page: www.sequel-software/downloads

    Originally Posted By richg

  • DB owner

    A user account must be the db_owner in order to access the table with the jdbc connections used in Sequel.

    Originally Posted By richg

  • Get lib/file name

    There are no expressions to directly retrieve the library/file name in use and display in a column.  However, if you can populate a data area with that detail before running the view in a cl pgm or a script, then you can use the DTAARA command to retriive and display that data.


    Returns a variable length character string up to 200 characters long containing the extracted substring from the indicated data area. Only the first 2000 positions of the data area are accessible. The 'object name' string can contain a fully qualified name (lib/obj) or an unqualified name, or one of the special values *LDA, *GDA, or *PDA.

    DTAARA(["objname",] start, length)

    Originally Posted By richg

  • Unique Keys

    Here is where I would start:

    Unique Keys

    If an ORDER BY clause is specified, UNIQUEKEY can be used to retrieve only the first record in a series that matches a given ordering value. The parameter is ignored unless the ORDER BY clause is specified. Refer to the description of the ORDER BY clause in the Structure of SEQUEL Statements section for a complete explanation of ORDER BY and UNIQUEKEY.

    Use of UNIQUEKEY restricts the view to input operations. It is not updateable - the UPDATE and DELETE commands cannot use a view with UNIQUEKEY specified. In addition, the OPNSQLF command will not allow any open options except input (*INP).

    *NONE: indicates that the uniqueness of the ordering paths not to be tested and used in retrieving the records. All records included in the view will be presented.

    *ALL: specifies that the entire ordering specification should be used in the uniqueness test.

    integer: only this number of fields (the leftmost being first) will be used in the uniqueness test. The remaining ordering fields are used in determining which record from the series with like values will be presented. The first record in each set will appear in the view.

    Originally Posted By jpyatt

  • Julie,This should work.


    This should work.  Leave the &NUM variable just the way you have it so you are prompted for the value.





    Originally Posted By jpyatt

  • There is a special file

    There is a special file called SQDATE in the SEQUEL library that will contain one row for a date range.  You can populate the SQDATE with a command called: SQDATE,  prompt the command and specify your start/end date range.  Usually you would build this file for several years worth of date fields.  Then use the file as file number 1 with a parital outer join and select your range with a start/end date variable and pick whichever date day dispaly format you want to see as your first column.  This will produce one row of output for each day in the date range.

    Originally Posted By richg

  • Date in each row

    There are no expressions available to create a row for each date within a date range.  Generally, you can not create rows of data in a view result.  You can consider using a special file called SQDATE in the SEQUELEX library.  You may need to create the file with a start/end date range.  Use the SQDATE command to create the file.  Then use the file in a join to select a range of daily date records based onn the start/end inputs from the view variables.

    Originally Posted By richg

  • Reply to: How does RODIN handle development and production?

    Hi Ragul,

    That's a great question, and I realized it has been asked before, so instead of replying here I have created a FAQ article: RODIN Change Management

    In regard to integrating with your home grown change management, it is quite likely to be possible. We will need to discuss and look at it's capabilities.

    Originally Posted By AJ