It should work going from Windows to RHEL without conversion. 

Going from the same version of Cache to the same version, e.g. 2015.1 to 2015.1 should work without any changes.  Going to a newer version, one should follow the appropriate upgrade procedures in the documentation for the particular version.

Going back versions can present multiple problems and is not recommended.  If you were to want to go from say 2015.1 to 2014.1, you would most likely want to export and import data, classes and routines.  From one version to another, new keywords and classes, etc may have been added that are not compatible with older versions.

Some platforms do have different endian versions, for example, going from Windows to AIX on PowerPC requires the cvendian tool to be run to convert the the endian versions.

In Cache, due to the way we store data on disk, partitioning the data may not give you a significant benefit in access time.  Data is stored in a highly optimized fashion and the effort to retrieve a record stored at the "top" of a table takes no more effort to retrieve than a record stored at the "bottom" of a table.

If you have records within a table that need to be located quicker (different than being retrieved from disk) you may want to consider setting up some useful indexes that you can use to locate specific records within the table.

Do you have an example of your table structure and could you explain what you mean by more frequently accessed data?

You could use %GOF for export and %GIF for import from Terminal.   These tools export block level data.   The ultimate size of the export will be much less than other tools 

Is this a one-time migration of data from instance A to instance B?

If so, create a new database on instance A and then use GBLOCKCOPY to copy from the existing database to the new one.   Then just move the new database to instance B

There are lots of terms here that although may be related really pertain to different things.

This post mentions client/server and services and applications.  Both services and applications can be implemented in a client/server architecture.

A service is an application that typically has a client and a server side component.  Common types of web services are SOAP web services and RESTful web services.   They usually provide some very specific function.  For example; a USPS address verification service does nothing but receive a message containing an address that needs to be verified, verifies it, and then sends a response message back to the client with the results of that verification.

An application can also be developed using a client/server architecture where there is a software component that runs on the client and a separate software component that runs on the server.  Unlike a service, in a client/server application business logic may be handled at either the client or the server, or both, allowing for distribution of resources.  The client and server parts of an application typically communicate with each other using services.

CSP and Zen, as well as other technologies like PHP, Java Server Pages, ASP.Net are all server-side scripting languages.  The purpose of each is to generate some dynamic document that is then sent to a web-browser by a web server and then rendered (or presented) to the user by a web browser running on the user's computer.  Both Zen and CSP allow you to embed Javascript within the document in various ways.  Javascript is executable code that is run within the web browser.  Typically Javascript is used for form validation and different interactions between the various parts of a web-page.  It prevents the need to have to call the server every time that you want to update a web page.

This suggestion solved my problem.

 

WorkflowPurge

            s c=0

            &sql(DECLARE tieCursor CURSOR FOR

            SELECT

            ID into :ID

            FROM EnsLib_Workflow.TaskResponse)    

            &sql(OPEN tieCursor)

            FOR

            {

                        &sql(FETCH tieCursor)

                        Quit:SQLCODE

                        w !,ID

                        s c=$G(c)+1

                        s tTask=##class(EnsLib.Workflow.TaskResponse).%OpenId(ID)

                        set tSC = ##class(EnsLib.Workflow.Engine).CompleteTask(tTask)

                       

            }

            &sql(CLOSE tieCursor)

So I finally found the place to add code packages under My Content -> My Collaborations.  It seems that it would be more intuitive if when I searched for code packages, if I didnt find what I was looking for that I should be able to add something right there.  

 

As someone who might post a code package I would probably want to see if it already existed first, and then if it didnt already exist then I would have the option to add it.