Hello Charles,

Thank you for telling me about the Dallas Remote Development program. From your description, it appears to provide exactly the type of environment Lua/TSO requires: an isolated system that can be configured freely, IPLed when necessary, and run with a current version of z/OS.

Unfortunately, a price of approximately $550 per month is too high for this project.

Lua/TSO is a non-commercial open-source project released under the Apache-2.0 license and developed independently by me. It has no sponsoring company, commercial customers, or institutional funding. At that rate, the environment would cost approximately $6,600 per year.

I am not developing the project for profit. I am interested in the architecture of z/OS and in creating a modern system automation environment for the platform. If the result proves useful to the IBM Z community, that would be the project's primary value.

Lua/TSO is also developed in my spare time outside my main job. Progress will inevitably be uneven: periods of active development may be followed by pauses lasting several days or weeks. During those pauses, I could shut down the LPAR or virtual machine completely so that it would not consume computing resources.

For that reason, a fixed monthly fee does not fit the actual usage pattern very well. A model based on actual runtime, with only storage costs while the environment is stopped, would be much more suitable for a project like this.

I do not need production capacity, high performance, an SLA, or permission for commercial use. A small isolated environment would be sufficient, provided that it allows me to:

• stop it during periods of inactivity;
• preserve its state and resume work later;
• pay for actual usage or a small storage fee while stopped;
• use it solely for development of the public Lua/TSO project;
• exclude performance testing and all production workloads.

Lua/TSO requires more than a normal user account because I need to validate installation procedures, RACF profiles, started tasks, authorized libraries, and integration with native z/OS system services. This requires a separate recoverable VM or LPAR, but it does not need to run continuously.

Do you know whether Dallas Remote Development offers any of the following?

1. A reduced-cost plan for independent open-source developers.
2. Billing based only on actual environment runtime.
3. The ability to stop the LPAR for extended periods and pay only for storage.
4. Sponsored access through IBM, the Open Mainframe Project, or another organization.
5. A contact who could review Lua/TSO as a non-commercial open-source project.

If Dallas is available only to commercial ISVs under a fixed monthly subscription, then unfortunately it does not solve the access problem for this project. However, it does show that the required technical environment already exists. What is missing is an affordable and legitimate path for independent open-source development.

I would appreciate any contact or possible alternative you can suggest.

Thank you again for the concrete lead.

Regards,

Ruslan Stepanenko
Lua/TSO project author
https://github.com/drblez/luaz

Hello Charles,

Thank you for telling me about the Dallas Remote Development program. From your description, it appears to provide exactly the type of environment Lua/TSO requires: an isolated system that can be configured freely, IPLed when necessary, and run with a current version of z/OS.

Unfortunately, a price of approximately $550 per month is too high for this project.

Lua/TSO is a non-commercial open-source project released under the Apache-2.0 license and developed independently by me. It has no sponsoring company, commercial customers, or institutional funding. At that rate, the environment would cost approximately $6,600 per year.

I am not developing the project for profit. I am interested in the architecture of z/OS and in creating a modern system automation environment for the platform. If the result proves useful to the IBM Z community, that would be the project's primary value.

Lua/TSO is also developed in my spare time outside my main job. Progress will inevitably be uneven: periods of active development may be followed by pauses lasting several days or weeks. During those pauses, I could shut down the LPAR or virtual machine completely so that it would not consume computing resources.

For that reason, a fixed monthly fee does not fit the actual usage pattern very well. A model based on actual runtime, with only storage costs while the environment is stopped, would be much more suitable for a project like this.

I do not need production capacity, high performance, an SLA, or permission for commercial use. A small isolated environment would be sufficient, provided that it allows me to:

• stop it during periods of inactivity;
• preserve its state and resume work later;
• pay for actual usage or a small storage fee while stopped;
• use it solely for development of the public Lua/TSO project;
• exclude performance testing and all production workloads.

Lua/TSO requires more than a normal user account because I need to validate installation procedures, RACF profiles, started tasks, authorized libraries, and integration with native z/OS system services. This requires a separate recoverable VM or LPAR, but it does not need to run continuously.

Do you know whether Dallas Remote Development offers any of the following?

1. A reduced-cost plan for independent open-source developers.
2. Billing based only on actual environment runtime.
3. The ability to stop the LPAR for extended periods and pay only for storage.
4. Sponsored access through IBM, the Open Mainframe Project, or another organization.
5. A contact who could review Lua/TSO as a non-commercial open-source project.

If Dallas is available only to commercial ISVs under a fixed monthly subscription, then unfortunately it does not solve the access problem for this project. However, it does show that the required technical environment already exists. What is missing is an affordable and legitimate path for independent open-source development.

I would appreciate any contact or possible alternative you can suggest.

Thank you again for the concrete lead.

Regards,

Ruslan Stepanenko
Lua/TSO project author
https://github.com/drblez/luaz

Hello Charles,

Thank you for telling me about the Dallas Remote Development program. From your description, it appears to provide exactly the type of environment Lua/TSO requires: an isolated system that can be configured freely, IPLed when necessary, and run with a current version of z/OS.

Unfortunately, a price of approximately $550 per month is too high for this project.

Lua/TSO is a non-commercial open-source project released under the Apache-2.0 license and developed independently by me. It has no sponsoring company, commercial customers, or institutional funding. At that rate, the environment would cost approximately $6,600 per year.

I am not developing the project for profit. I am interested in the architecture of z/OS and in creating a modern system automation environment for the platform. If the result proves useful to the IBM Z community, that would be the project's primary value.

Lua/TSO is also developed in my spare time outside my main job. Progress will inevitably be uneven: periods of active development may be followed by pauses lasting several days or weeks. During those pauses, I could shut down the LPAR or virtual machine completely so that it would not consume computing resources.

For that reason, a fixed monthly fee does not fit the actual usage pattern very well. A model based on actual runtime, with only storage costs while the environment is stopped, would be much more suitable for a project like this.

I do not need production capacity, high performance, an SLA, or permission for commercial use. A small isolated environment would be sufficient, provided that it allows me to:

• stop it during periods of inactivity;
• preserve its state and resume work later;
• pay for actual usage or a small storage fee while stopped;
• use it solely for development of the public Lua/TSO project;
• exclude performance testing and all production workloads.

Lua/TSO requires more than a normal user account because I need to validate installation procedures, RACF profiles, started tasks, authorized libraries, and integration with native z/OS system services. This requires a separate recoverable VM or LPAR, but it does not need to run continuously.

Do you know whether Dallas Remote Development offers any of the following?

1. A reduced-cost plan for independent open-source developers.
2. Billing based only on actual environment runtime.
3. The ability to stop the LPAR for extended periods and pay only for storage.
4. Sponsored access through IBM, the Open Mainframe Project, or another organization.
5. A contact who could review Lua/TSO as a non-commercial open-source project.

If Dallas is available only to commercial ISVs under a fixed monthly subscription, then unfortunately it does not solve the access problem for this project. However, it does show that the required technical environment already exists. What is missing is an affordable and legitimate path for independent open-source development.

I would appreciate any contact or possible alternative you can suggest.

Thank you again for the concrete lead.

Regards,

Ruslan Stepanenko
Lua/TSO project author
https://github.com/drblez/luaz

Hello Charles,

Thank you for telling me about the Dallas Remote Development program. From your description, it appears to provide exactly the type of environment Lua/TSO requires: an isolated system that can be configured freely, IPLed when necessary, and run with a current version of z/OS.

Unfortunately, a price of approximately $550 per month is too high for this project.

Lua/TSO is a non-commercial open-source project released under the Apache-2.0 license and developed independently by me. It has no sponsoring company, commercial customers, or institutional funding. At that rate, the environment would cost approximately $6,600 per year.

I am not developing the project for profit. I am interested in the architecture of z/OS and in creating a modern system automation environment for the platform. If the result proves useful to the IBM Z community, that would be the project's primary value.

Lua/TSO is also developed in my spare time outside my main job. Progress will inevitably be uneven: periods of active development may be followed by pauses lasting several days or weeks. During those pauses, I could shut down the LPAR or virtual machine completely so that it would not consume computing resources.

For that reason, a fixed monthly fee does not fit the actual usage pattern very well. A model based on actual runtime, with only storage costs while the environment is stopped, would be much more suitable for a project like this.

I do not need production capacity, high performance, an SLA, or permission for commercial use. A small isolated environment would be sufficient, provided that it allows me to:

• stop it during periods of inactivity;
• preserve its state and resume work later;
• pay for actual usage or a small storage fee while stopped;
• use it solely for development of the public Lua/TSO project;
• exclude performance testing and all production workloads.

Lua/TSO requires more than a normal user account because I need to validate installation procedures, RACF profiles, started tasks, authorized libraries, and integration with native z/OS system services. This requires a separate recoverable VM or LPAR, but it does not need to run continuously.

Do you know whether Dallas Remote Development offers any of the following?

1. A reduced-cost plan for independent open-source developers.
2. Billing based only on actual environment runtime.
3. The ability to stop the LPAR for extended periods and pay only for storage.
4. Sponsored access through IBM, the Open Mainframe Project, or another organization.
5. A contact who could review Lua/TSO as a non-commercial open-source project.

If Dallas is available only to commercial ISVs under a fixed monthly subscription, then unfortunately it does not solve the access problem for this project. However, it does show that the required technical environment already exists. What is missing is an affordable and legitimate path for independent open-source development.

I would appreciate any contact or possible alternative you can suggest.

Thank you again for the concrete lead.

Regards,

Ruslan Stepanenko
Lua/TSO project author
https://github.com/drblez/luaz

Hello Charles,

Thank you for telling me about the Dallas Remote Development program. From your description, it appears to provide exactly the type of environment Lua/TSO requires: an isolated system that can be configured freely, IPLed when necessary, and run with a current version of z/OS.

Unfortunately, a price of approximately $550 per month is too high for this project.

Lua/TSO is a non-commercial open-source project released under the Apache-2.0 license and developed independently by me. It has no sponsoring company, commercial customers, or institutional funding. At that rate, the environment would cost approximately $6,600 per year.

I am not developing the project for profit. I am interested in the architecture of z/OS and in creating a modern system automation environment for the platform. If the result proves useful to the IBM Z community, that would be the project's primary value.

Lua/TSO is also developed in my spare time outside my main job. Progress will inevitably be uneven: periods of active development may be followed by pauses lasting several days or weeks. During those pauses, I could shut down the LPAR or virtual machine completely so that it would not consume computing resources.

For that reason, a fixed monthly fee does not fit the actual usage pattern very well. A model based on actual runtime, with only storage costs while the environment is stopped, would be much more suitable for a project like this.

I do not need production capacity, high performance, an SLA, or permission for commercial use. A small isolated environment would be sufficient, provided that it allows me to:

• stop it during periods of inactivity;
• preserve its state and resume work later;
• pay for actual usage or a small storage fee while stopped;
• use it solely for development of the public Lua/TSO project;
• exclude performance testing and all production workloads.

Lua/TSO requires more than a normal user account because I need to validate installation procedures, RACF profiles, started tasks, authorized libraries, and integration with native z/OS system services. This requires a separate recoverable VM or LPAR, but it does not need to run continuously.

Do you know whether Dallas Remote Development offers any of the following?

1. A reduced-cost plan for independent open-source developers.
2. Billing based only on actual environment runtime.
3. The ability to stop the LPAR for extended periods and pay only for storage.
4. Sponsored access through IBM, the Open Mainframe Project, or another organization.
5. A contact who could review Lua/TSO as a non-commercial open-source project.

If Dallas is available only to commercial ISVs under a fixed monthly subscription, then unfortunately it does not solve the access problem for this project. However, it does show that the required technical environment already exists. What is missing is an affordable and legitimate path for independent open-source development.

I would appreciate any contact or possible alternative you can suggest.

Thank you again for the concrete lead.

Regards,

Ruslan Stepanenko
Lua/TSO project author
https://github.com/drblez/luaz