This section describes resolved CRs, updates, and clarifications in EC Gateway.
CR# |
Description |
|---|---|
445882 |
Problem: An overflow error was received when the TPKEY went above 32767. Resolution: TPKEY can now exceed 32767. |
470332 |
Problem: A SySAM license check failure occurs when users rename wsproces.exe. Resolution: The SySAM licence check works now as expected. Users can rename wsproces.exe to any name of any length. |
472236 |
Problem: If you use Microsoft SQL Server, and then you use a substitute input file name in the Option 2 tab or use File Alias, then execute the RunMapOut command, an error message displays. Resolution: CR has been fixed. |
472806 |
Problem: The “Modify All Script File” option is dimmed when you right-click a “Do” command. Resolution: “Modify All Script File” option is now enabled. |
474627 |
Problem: A SySAM error prompts for a larger CPU number when there are already sufficient licences for each physical CPU. Resolution: SySAM now returns the correct CPU count. |
480094 |
Problem: The information in the fields in the OBDC Alias tab for inbound and outbound maps displays incorrectly. Passwords display in clear text and are not encrypted. Resolution: These fields now display information correctly. |
If your script includes multiple GetMessage statements, you must include explicit commands to move messages on and off the queue.
Each GetMessage statement gets a message from the queue; the message remains on the queue but is marked as having been read. To permanently remove the message from the queue, use a RemoveMessage command. To replace the message on the queue, as though it had not been read, use the RestoreMessage command.
If you want Scheduler to run tasks from the end of one year to a next date in the upcoming year, check the End Date/Time values in Advanced Scheduling. Set the correct field values or disable them completely.
Scheduling year-end processing
Start the Scheduler module.
Click Task and choose Add, or right-click a task and choose Edit.
Select the Scheduler tab. From the Frequency drop-down list, select Monthly.
In the Properties group, select Run each month(s) using the next scheduled.
Click Months, then select the months you want to schedule the run.
Click Advance Scheduling. Either:
Verify the End Date/Time fields values are correct, or
Deselect the End Date/Time check box. You must deselect this value for monthly transactions to cross yearly boundaries.
You can use the -r switch followed by the number of seconds to set the scheduling resolution from the command line when you start the UNIX Scheduler daemon. Sybase recommends a time greater than 5 seconds and less than 60 seconds, depending on the frequency and number of tasks you need to run.
Although the amount of free space you require to upgrade the log table varies, the amount of free space in the database should be greater than the size (including data) of the TRLOG current log table. If the amount of free space is greater, the upgrade should succeed.
wsproces command line arguments support parameter passing, including run IDs for 997 maps. The switches for these parameters are –p1 to –p20. With these switches, you can pass parameters from the command line to scripts. This feature is supported by both the wsproces DLL and executable. See the EDI Products 5.1 New Features Guide for additional information.
See the EDI Products 5.1 New Features Guide for a list of current and obsolete switches.
Table 5, Table 6, and Table 7 contain additional documentation about the ACKTA1, SYS_SECU, and PWD_GEN database tables respectively.
Column name |
Data type |
Length |
Description |
|---|---|---|---|
RUN_ID |
Integer |
9 |
Normal Run ID |
RUN_DATE |
Date/Time |
8 |
Normal run date |
SEND_QUAL |
Alphanumeric |
4 |
Sender qualifier from originating interchange |
SEND_CODE |
Alphanumeric |
35 |
Sender code from originating interchange |
RECV_QUAL |
Alphanumeric |
4 |
Receiver qualifier form originating interchange |
RECV_CODE |
Alphanumeric |
35 |
Receiver code from originating interchange |
INTERCHANG |
Alphanumeric |
35 |
Interchange control number |
ORIG_INT_NUM |
Alphanumeric |
35 |
Interchange control number from originating interchange |
ORIG_DATE |
Alphanumeric |
6 |
Date of originating interchange |
ORIG_TIME |
Alphanumeric |
4 |
Time of originating interchange |
INT_ACK_CD |
Alphanumeric |
1 |
Acknowledgment code for originating interchange (Accepted, Rejected, and so on) |
INT_NOTE_CD |
Alphanumeric |
3 |
Type of error (if any) for the originating interchange |
Column name |
Data type |
Length |
Description |
|---|---|---|---|
GW_VERSION |
Alphanumeric |
50 |
Gateway version number |
ONE_USERID |
Alphanumeric |
1 |
Flag for unique user ID for communications channels |
ONE_LOGIN |
Alphanumeric |
1 |
Flag for unique login for each communications channel |
ONE_ALPHA |
Alphanumeric |
1 |
Flag for at least one alphabetic character in the password of communications channels |
ONE_DIGIT |
Alphanumeric |
1 |
Flag for at least one numeric character in the password of asynchronous channels |
PWD_MINLEN |
Integer |
10 |
Minimum password length in communications channels |
BAD_ATTEMP |
Integer |
10 |
Lockout after bad attempts |
PWD_EXPIRE |
Integer |
10 |
Password expires after days |
PWD_GEN |
Integer |
10 |
Generations for password history |
Column name |
Data type |
Length |
Description |
|---|---|---|---|
USER_ID |
Alphanumeric |
50 |
User ID for the gateway communications channels |
USER_TYPE |
Alphanumeric |
50 |
Communication channel type |
PWD_GEN |
Integer |
10 |
Which generation for the password history |
USER_PWD |
Alphanumeric |
50 |
Password for the gateway communications channels |
