User Answers

Hi Leon,

You're actually looking to create a batch, with a batch header for your file output.

To do this you'll need to define a batch class in your RecordMap, and in that class define your header (I'm assuming it's a fixed header, like field names).

You'll then want to use EnsLib.RecordMap.Operation.BatchFileOperation (or BatchFTPOperation) to deliver the batches. There are a few ways to trigger the batch rollover; a schedule, a record limit, or a Batch Rollover Request depending on your needs.

I'm thinking that you may want quotes around the 0000 value ... you are, after all comparing it to a string laugh

Hi Robert,

You can actually export the entire production in a single go through the Export button found in the Actions tab of the Production Settings. You would then use the "Manage / Deployment Changes" page on the target system to deploy the entire production to the destination namespace.


You were close with you original code ...

Set newreq = request.%ConstructClone()

Set sc = newreq.RemoveSegmentAt("EVN")

Set request = newreq

the variable sc is the status of the remove segment operation; the EVN segment is actually removed from newreq.


You can use the Source property to identify the component that sent the message into the router:


I've cobbled together a little TamperMonkey/GreaseMonkey script that diddles with the style sheet without having to make unsupported changes to your installation's configuration. Adust the devattr, qaattr and prdattr variables to suit your color tastes, and the match arguments for the hostnames to identify your servers.

You could do it with an SQL query:

DELETE FROM Ens_Util.LookupTable WHERE TableName = '<name of table>'

You can create the query either via the Management Console (System Explorer | SQL | Execute Query tab) or from the SQL Shell

As @Brian Schoen alluded to, $CHAR -- abbreviated to $C if you want to be one of the cool kids -- is what you need. $C(13,10) is the line-end sequence in Windows. $C(10) is Unix. $C(13), though, is old-school Macintosh* laugh



%SYS>d ##class(Config.Startup).Get(.Prop)

%SYS>w Prop("WebServerPort")


If you're interested in just examining the headers and body generated by your request, you can install Postman and use it as a proxy. It will capture everything for you and present it in a very readable format.