I-Series System Processes
(Last Update 6/19/2002)


    The CIM system is controlled and utilized through a series of I-series menus, commands, and background processes.  The following sections describe these.

CIM Background Processes:

CIM Commands:

    The following commands are available from any DAC Menu command line.

Command Explanation
EDIAFXM
Overview
The EDIAFXM command is used to monitor a local I-Series file-system folder and a remote FTP-site folder for files that need to be exchanged. This facilitates the automatic, unattended exchange of CIM data files.  The command performs these functions:
  • Connects to a specified FTP site
  • Looks in a specified local folder for CIM files. Any files found there are sent to a specified remote folder and removed from the local folder.
  • Looks in a specified remote folder for CIM files.  Any files found there are sent to a specified local folder and removed from the remote folder.
Parameters
Name - Keyword Description Values
Monitor for Inbound Files - INBOUND Indicates if the remote FTP server's file system should be monitored for files destined for the local system.  *NO - Folder should not be monitored on the remote system.

*YES -Folder should be monitored and retrieved from the remote system.
Name of Local FLR (Inbound) - LCLFLRIN Gives the name of a folder in the local files system into which files retrieved from the remote server should be placed. Valid folder name
Name of Remote FLR (Inbound) - RMTFLRIN Gives the name of the folder on the remote system from which files should be retrieved. Valid folder name
Monitor for Outbound Files - OUTBOUND Indicates if a local files system folder should be monitored for files destined for the remote system. *NO - Folder should not be monitored on the local system.

*YES - Local folder should be monitored and files sent to the remote system.
Name of Local FLR (Outbound) - LCLFLROUT Gives the name of a folder on the local system from which files should be sent to the remote system. Valid folder name
Name of Remote FLR (Outbound) - RMTFLROUT Gives the name of a folder on the remote system into which files from the local system should be placed. Valid folder name
Name of copy FLR (Outbound) - CPYFLROUT Gives the name of a folder on the local system into which files sent to the remote system will be copied.  This folder can be used to maintain an archive of successfully sent files.  Leave blank to perform no copy. Valid folder name
User ID for FTP Login - USER FTP User ID
Password for FTP Login - PASS FTP Password
Remote system name - RMTSYS IP address or host name of the remote FTP server
Poll Option - POLL Indicates how often the local and/or remote folders should be "polled" for existing files. *FOREVER - Continuously poll the specified local and/or remote folders.  Stop only when the EDI/CIM Interface is stopped.

*ONCE - Poll specified local and/or remote folders one time only, then quit.
Delay time between polling - DLY If poll option is *FOREVER, this value indicates how many seconds should transpire before the local and/or remote folders are polled again. Number of seconds 0 - 9999
Log CL Commands - LOG Used for diagnostic
Initiate PPP Connection - PPPINIT Indicates of a Point to Point protocol network connection should be established when the command is activated. *YES

*NO
PPP Profile - PPPPRF Used when PPP or Slip is desired network protocol. A valid Connection Profile as defined under the "Point-to-Point" section of the "Network" section in Operations Navigator.
Connection time allowance - PPPDLY If PPP or Slip is used, how many seconds should be allowed for a connection to be established before aborting.  Allow at least 60 seconds. 0 - 9999
Use Passive Mode - PASV Indicates if file transfers with the remote FTP server take place in Passive mode. *YES - Use passive mode

*NO - Do not use passive mode
 

 

EDIAIM
Overview
The EDIAIM command is used to monitor a local I-Series file-system for files to import.  The files are expected to contain CETE-based information, which is processed by the Transaction Gateway.  Once started, the command will continuously monitor the folder until the EDIEND command is issued (Or until the Interface is ended from the Interface Control Panel).
  • Opens the designated folder and checks for the existence of any folder document.
  • If a document is found, the contents are sent to the Transaction Gateway for processing.
  • The document is deleted.
Parameters
Name - Keyword Description Values
Name of Folder - FLR Gives the name of a folder to monitor for files. Valid folder name
Data Library - LIB Gives the name of the DAC data library to use.   DACDATA, *LIBL, or other library containing DAC data files. 

Example:

EDIAIM FLR('mailbox/in/pidf') LIB(DACDATA)
 

 

EDIAIMP
Overview
The EDIAIMP command is used to import a single folder document into the Transaction Gateway.  It is essentially the same as the EDIAIM command, except that it imports a given document, and immediately ends. The imported document is NOT deleted.
Parameters
Name - Keyword Description Values
Folder Name -  FLR Gives the name of a folder which contains the source document. Valid folder name
Folder Document - FLRDOC Gives the name of the source document. Document Name
Data Library - LIB Gives the name of the DAC data library to use.   DACDATA, *LIBL, or other library containing DAC data files.
Examples

EDIAIMP FLR('mailbox/in/123456') FLRDOC(ORDERS.DAT)

 

 

 

EDIAUTOSCH
Overview
The EDIAUTOSCH command is used to execute "Saved Scoped Dispatch Requests".  This provides a way to automate the dispatching or "dumping" of information.  Often, this command will be scheduled using the I-series job scheduler.  (For more information on using the I-Series Job Scheduler to automatically schedule the EDIAUTOSCH command, please refer to your OS/400 user's guide)
Parameters
Name - Keyword Description Values
Tag-  TAG Gives the tag name of the saved scoped dispatch request.  Only those having this tag name will be executed.  
 

 

EDIDQM
Overview
The EDIDQM command is used to monitor as OS/400 DATAQ object for CIM Messages.  These messages are imported into the Transaction Gateway and removed from the source DATAQ.
Parameters
Name - Keyword Description Values
Data Queue Name - DQNAME Dataq object name.  
Data Queue Library- DQLIB Name of the library in which the Data Queue is located.  
Data Library - LIB Gives the name of the DAC data library to use.   DACDATA, *LIBL, or other library containing DAC data files.

 

EDIEND
Overview
The EDIEND command is used to gracefully end all Integration Module tasks.  The command performs the same task as toggling the Interface to inactive from the Interface Control Panel.  The command has no parameters.
 

 

EDISTART
Overview
The EDIEND command is used to start all Integration Module tasks.  The command performs the same task as toggling the Interface to active from the Interface Control Panel.  The command has no parameters.

CIM Menus: 

CV1 Integration Module (INTCV1)

Interface Control Panel
The Interface Control Panel is used to start, stop, and define options for the Integration Module.  EDIDQM command is used to monitor as OS/400 DATAQ object for CIM Messages.  These messages are imported into the Transaction Gateway and removed from the source DATAQ.
Interface Control Panel Screen
Field Description Values
Interface Status Indicates if the Interface is active or inactive. Active/Inactive
System Mailbox Folder Identifies the root QDLS folder within which the primary folder structure is created. Defaults to MAILBOX
Activation Commands Gives a list of any commands that are issued when the Interface is toggled to Active.  The commands are submitted to batch in the same jobq as the Integration Module. Any valid OS/400 command.
Function Key Description
F2 Override active status and set to Inactive.
F3 Exit the control panel.
F5 Refresh the values on the screen.
F7 Work with Active Jobs (WRKACTJOB)
F8 Open the "Edit Interface Options" screen.
F10 Toggle from Active to Inactive or, from Inactive to Active.
"Edit Interface Options" screen.
Field Description Values
System Mailbox Folder Identifies the root QDLS folder within which the primary folder structure is created. Defaults to MAILBOX
Interface Job Queue Name of a Jobq which the Integration Module runs under. Any valid OS/400 JobQ.  Must allow *NOMAX on the number of jobs.
Flow Status Indicates of data may flow in and/or out of the system. I=Inbound only, O=Outbound only, B=Both Inbound and Outbound.
Network User Id A user ID used to send files via SNADS.  
Cust/Item Dispatch Scope. Indicates what degree of customer-specific item data is channeled through the system. See Screen for Values.
Activation Commands Gives a list of any commands that are issued when the Interface is toggled to Active.  The commands are submitted to batch in the same jobq as the Integration Module.  All CIM commands also terminate when the Interface is toggled to Inactive. Any valid OS/400 command.  Often, CIM commands (such as EDIAIM) are specified here.
Function Key Description
F3 Return to Interface Control Panel.
F4 Prompt activation command.

 

 

Item Dispatch
The Item Dispatch screen is used to generate and route item-related data to various targets.
Item Dispatch Screen
Field Description Values
Target Customer The customer to whom the item data is destined for. Valid customer target setup in the CIM system.  Customer targets may only receive item data to which they are authorized.  Wholesaler cost is not output when the target is a customer.
Target Employee The employee to whom the item data is destined for. Valid Employee target setup in the CIM system.
Target Super Target The employee to whom the item data is destined for. Valid Super Target setup in the CIM system.
General Item Data Indicates if topic "IT" should be included in generated data. Y/N
Warehouse-Specific Item Data Indicates if topic "IB" should be included in generated data. Y/N
Customer-Specific Item Data Indicates if topic "CI" should be included in generated data. Y/N  This opion is only available if the target is a customer or an employee.
Limit to Sales Class  Provides a way to limit the generated data to only include items belonging to a given sales class.  
Limit to Category Provides a way to limit the generated data to only include items belonging to a given category.  
Limit to Items that are associated with the target? Provides a way to limit the generated data to only include items which have a customer-item record for the customer target or  customer of the employee target. Y/N
Dispatch using normal channel? Indicates if the data should be generated according to all normal qualification and routing rules.  Y/N

Choose "Y" if you want the system to gradually send out the data through the normal channel using normal qualification rules.

Choose "N" if you want to send the data to an ASCII folder nad file.  If you choose "N", you must specify a valid QDLS folder and document.
Function Key Description
F3 Exit
F4 Prompt for a value.
F5 Resets the screen to the default values.
F6 Process the request.  (Certain data types will submit to batch)
F7 Save the request.  This option displays a dialog which will allow you to enter additional information about the saved request:

1.) Description - Enter descriptive text to help identify the saved request.

2.) AutoSchedule? - Enter "Y" if this saved request qualifies to be executed through the EDIAUTOSCH command.  

3.) Tag - Enter a tag name.  This "Tag" can be used to further limit which saved request the EDIAUTOSCH command will execute.
F8 Select a previously saved scoped dispatch request.