date:20140930

[Oorexx-users] Is it possible to prevent end-users from reading a REXX program you're giving to them?

2014-09-30 Thread Bertram Moshier

Hi!

(I looked around for this topic using Google, but didn't find anything
before posting here.  If there is a better search facility, please, let me
know.)

I'm working on several programs for various people, but don't want to share
the source code.  I'm wondering if there is a way to protect a program you
write from an user either reading and/or modifying the code?  If yes,
great!  Ah, what is it?  If no, how can I submit this as a feature request
for a future release.  Specifically, if it is a new feature the
requirements I see are:

The programmer can set the ooRexx program file so the user can:

   - Only read but can't make changes the ooRexx interpreter will recognize.
   - Neither read nor modify any program.
   - Allow the end user to read and modify the program, but require a new
   program name for the saved program.
   - Allow the end user to read and save the original program.

My thought on how to implement would be a new exe file / program to create
and maintain these program files.  The rexx.exe, dll, etc would need to
know how to read the new binary files.NOTE:  I don't look at this as a
compiler but closer to encryption of the ooRexx program.

(As for US export, the encrypt / decrypt) could be an user-exit supplied by
the programmer.  What would come with ooRexx is a simple template that
would do something similar to zip, which should be OK for release
worldwide.)

Thank you,

Bert.
--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users

[Oorexx-users] Reading file opened by a second program

2014-09-30 Thread Bertram Moshier

Hello again,

I'm still stumped on how to read a file opened by a second program for
writing.  I know I'm not chasing after windmills, as the copy and type
commands BOTH can read the file, while the other program has it open for
writing.

Yet, as previously, mentioned what I get back from Rexx are blank / null
lines.  The lines function correctly sees the number of lines in the file,
but when Rexx reads the file the lines it returns to the program are null.
Yet, when either the type or copy commands look at the file, they see
data/content in the file.

At this point, my guess is there is a bug in Rexx and/or the need for a
feature.  At this point I'm asking:


   - Is there something else I can try within Rexx and if not:
   - How do I determine if this is a bug or the need for a feature?

Thank you,

Bert.
--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users

Re: [Oorexx-users] Reading file opened by a second program

2014-09-30 Thread Rick McGuire

If you think you have a bug, then create a program that would allow a
developer to reproduce the problem and open a bug report.  The location for
opening a bug report is here:

https://sourceforge.net/p/oorexx/bugs/

Generally, it is impossible to answer questions like this without seeing
exactly what you are doing.  I can't speak for others, but I won't even
attempt to answer the is this a bug type questions until I have an open
bug report and am able to reproduce the problem myself.

Rick

On Tue, Sep 30, 2014 at 12:06 PM, Bertram Moshier bertrammosh...@gmail.com
wrote:

 Hello again,

 I'm still stumped on how to read a file opened by a second program for
 writing.  I know I'm not chasing after windmills, as the copy and type
 commands BOTH can read the file, while the other program has it open for
 writing.

 Yet, as previously, mentioned what I get back from Rexx are blank / null
 lines.  The lines function correctly sees the number of lines in the file,
 but when Rexx reads the file the lines it returns to the program are null.
 Yet, when either the type or copy commands look at the file, they see
 data/content in the file.

 At this point, my guess is there is a bug in Rexx and/or the need for a
 feature.  At this point I'm asking:


- Is there something else I can try within Rexx and if not:
- How do I determine if this is a bug or the need for a feature?

 Thank you,

 Bert.


 --
 Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
 Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
 Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
 Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer

 http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
 ___
 Oorexx-users mailing list
 Oorexx-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/oorexx-users


--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users

[Oorexx-users] ooSQLite 10584 compile problem

2014-09-30 Thread Staffan Tylen

Hi Mike, I'm trying to compile the latest available source for ooSQLite but
am receiving loads of error messages. I've updated my makefile to include
recent changes in makefile.win. Below are the messages I receive.

Microsoft (R) Program Maintenance Utility Version 11.00.60610.1
Copyright (C) Microsoft Corporation.  All rights reserved.

D:\ooRexx\ooSQLite\src
cl /nologo /EHsc /O2 /Gs /Gy /FAs /Fabuild\release\ /MT /W3
/D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE
/DOOSQLITE_VER_MAJOR=1 /DOO
SQLITE_VER_MINOR=0 /DOOSQLITE_VER_LEVEL=0 /DOOSQLITE_VER_BUILD=10584
/DOOSQLITE_VER_STRING=\1.0.0.10584\
/DOOSQLITE_COPYRIGHT_YEAR=\2012-2013\
 /I src\sqlite /I src\platform\windows /I
..\ooRexx.4.1\extensions\platform\windows\oodialog
/DSQLITE_ENABLE_COLUMN_METADATA /DSQLITE_ENABLE_MEMORY_MA
NAGEMENT /DSQLITE_ENABLE_FTS3 /DSQLITE_ENABLE_FTS3_PARENTHESIS
/DSQLITE_DEFAULT_FOREIGN_KEYS=1 /DSQLITE_CORE /DSQLITE_HAS_CODEC
/DSQLITE_MAX_COLUMN=32
767 /DHAVE_STDINT_H /D:_X86_ /DWIN32 /DNDEBUG /DNULL=0 /c /DOOSQLITE_BUILD
/Fo.\build\release\ src\sqlite\sqlite3_with_codec.c
sqlite3_with_codec.c
cl /nologo /EHsc /O2 /Gs /Gy /FAs /Fabuild\release\ /MT /W3
/D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE
/DOOSQLITE_VER_MAJOR=1 /DOO
SQLITE_VER_MINOR=0 /DOOSQLITE_VER_LEVEL=0 /DOOSQLITE_VER_BUILD=10584
/DOOSQLITE_VER_STRING=\1.0.0.10584\
/DOOSQLITE_COPYRIGHT_YEAR=\2012-2013\
 /I src\sqlite /I src\platform\windows /I
..\ooRexx.4.1\extensions\platform\windows\oodialog
/DSQLITE_ENABLE_COLUMN_METADATA /DSQLITE_ENABLE_MEMORY_MA
NAGEMENT /DSQLITE_ENABLE_FTS3 /DSQLITE_ENABLE_FTS3_PARENTHESIS
/DSQLITE_DEFAULT_FOREIGN_KEYS=1 /DSQLITE_CORE /DSQLITE_HAS_CODEC
/DSQLITE_MAX_COLUMN=32
767 /DHAVE_STDINT_H /D:_X86_ /DWIN32 /DNDEBUG /DNULL=0 /c /DOOSQLITE_BUILD
/Fo.\build\release\ src\ooSQLite.cpp
ooSQLite.cpp
src\ooSQLite.cpp(89) : error C3861: 'packageLoadHelper': identifier not
found
src\ooSQLite.cpp(94) : error C2065: 'TheDotLocalObj' : undeclared identifier
src\ooSQLite.cpp(159) : error C2065: 'TheDotLocalObj' : undeclared
identifier
src\ooSQLite.cpp(164) : error C2065: 'TheDotLocalObj' : undeclared
identifier
src\ooSQLite.cpp(443) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(574) : error C2664: 'stringTooLongException' : cannot
convert parameter 2 from 'const char [8]' to 'size_t'
There is no context in which this conversion is possible
src\ooSQLite.cpp(819) : error C2065: 'TheZeroObj' : undeclared identifier
src\ooSQLite.cpp(870) : error C2065: 'TheZeroObj' : undeclared identifier
src\ooSQLite.cpp(1371) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(1443) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(1503) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(1582) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(1586) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(1664) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(1735) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(1796) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(1863) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(1932) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(2007) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(2074) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(2174) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(2195) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(2254) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(2304) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(2602) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(2670) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(2751) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(2773) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(2782) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(3331) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(3406) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(3608) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(3640) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(3653) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(3687) : error C2065: 'TheZeroPointerObj' : undeclared
identifier
src\ooSQLite.cpp(3962) : error C2065: 'TheZeroObj' : undeclared identifier
src\ooSQLite.cpp(4118) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(4201) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(4269) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(4376) : error C2065: 'TheNilObj' : undeclared identifier
src\ooSQLite.cpp(4884) : error C2065: 'TheZeroObj' : undeclared

Re: [Oorexx-users] ooSQLite 10584 compile problem

2014-09-30 Thread hexit34

Staffan

Have you done this


Changes needed for compilation of SQLITE amalgation to oosqlite 
-
Last in sqlite3.c module ADD


#ifdef OOSQLITE_BUILD
SQLITE_API const sqlite3_api_routines* oosqlite3_get_routines(void){
return sqlite3Apis;
}
#endif


--
Last in sqlite3.h ADD


#ifdef OOSQLITE_BUILD


#ifdef __cplusplus
extern C {
#endif


typedef struct sqlite3_api_routines sqlite3_api_routines;
extern SQLITE_API const sqlite3_api_routines *oosqlite3_get_routines(void);


#ifdef __cplusplus
}  /* end of the 'extern C' block */
#endif


#endif /* end if OOSQLITE_BUILD */






Skickat från Windows E-post





Från: Staffan Tylen
Skickat: ‎tisdag‎ den ‎30‎ ‎september‎ ‎2014 ‎21‎:‎42
Till: Open Object Rexx Users





Hi Mike, I'm trying to compile the latest available source for ooSQLite but am 
receiving loads of error messages. I've updated my makefile to include recent 
changes in makefile.win. Below are the messages I receive.




Microsoft (R) Program Maintenance Utility Version 11.00.60610.1

Copyright (C) Microsoft Corporation.  All rights reserved.




D:\ooRexx\ooSQLite\src

cl /nologo /EHsc /O2 /Gs /Gy /FAs /Fabuild\release\ /MT /W3 
/D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE /DOOSQLITE_VER_MAJOR=1 
/DOO

SQLITE_VER_MINOR=0 /DOOSQLITE_VER_LEVEL=0 /DOOSQLITE_VER_BUILD=10584 
/DOOSQLITE_VER_STRING=\1.0.0.10584\ 
/DOOSQLITE_COPYRIGHT_YEAR=\2012-2013\

 /I src\sqlite /I src\platform\windows /I 
..\ooRexx.4.1\extensions\platform\windows\oodialog 
/DSQLITE_ENABLE_COLUMN_METADATA /DSQLITE_ENABLE_MEMORY_MA

NAGEMENT /DSQLITE_ENABLE_FTS3 /DSQLITE_ENABLE_FTS3_PARENTHESIS 
/DSQLITE_DEFAULT_FOREIGN_KEYS=1 /DSQLITE_CORE /DSQLITE_HAS_CODEC 
/DSQLITE_MAX_COLUMN=32

767 /DHAVE_STDINT_H /D:_X86_ /DWIN32 /DNDEBUG /DNULL=0 /c /DOOSQLITE_BUILD 
/Fo.\build\release\ src\sqlite\sqlite3_with_codec.c

sqlite3_with_codec.c

cl /nologo /EHsc /O2 /Gs /Gy /FAs /Fabuild\release\ /MT /W3 
/D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE /DOOSQLITE_VER_MAJOR=1 
/DOO

SQLITE_VER_MINOR=0 /DOOSQLITE_VER_LEVEL=0 /DOOSQLITE_VER_BUILD=10584 
/DOOSQLITE_VER_STRING=\1.0.0.10584\ 
/DOOSQLITE_COPYRIGHT_YEAR=\2012-2013\

 /I src\sqlite /I src\platform\windows /I 
..\ooRexx.4.1\extensions\platform\windows\oodialog 
/DSQLITE_ENABLE_COLUMN_METADATA /DSQLITE_ENABLE_MEMORY_MA

NAGEMENT /DSQLITE_ENABLE_FTS3 /DSQLITE_ENABLE_FTS3_PARENTHESIS 
/DSQLITE_DEFAULT_FOREIGN_KEYS=1 /DSQLITE_CORE /DSQLITE_HAS_CODEC 
/DSQLITE_MAX_COLUMN=32

767 /DHAVE_STDINT_H /D:_X86_ /DWIN32 /DNDEBUG /DNULL=0 /c /DOOSQLITE_BUILD 
/Fo.\build\release\ src\ooSQLite.cpp

ooSQLite.cpp

src\ooSQLite.cpp(89) : error C3861: 'packageLoadHelper': identifier not found

src\ooSQLite.cpp(94) : error C2065: 'TheDotLocalObj' : undeclared identifier

src\ooSQLite.cpp(159) : error C2065: 'TheDotLocalObj' : undeclared identifier

src\ooSQLite.cpp(164) : error C2065: 'TheDotLocalObj' : undeclared identifier

src\ooSQLite.cpp(443) : error C2065: 'TheNilObj' : undeclared identifier

src\ooSQLite.cpp(574) : error C2664: 'stringTooLongException' : cannot convert 
parameter 2 from 'const char [8]' to 'size_t'

There is no context in which this conversion is possible

src\ooSQLite.cpp(819) : error C2065: 'TheZeroObj' : undeclared identifier

src\ooSQLite.cpp(870) : error C2065: 'TheZeroObj' : undeclared identifier

src\ooSQLite.cpp(1371) : error C2065: 'TheNilObj' : undeclared identifier

src\ooSQLite.cpp(1443) : error C2065: 'TheNilObj' : undeclared identifier

src\ooSQLite.cpp(1503) : error C2065: 'TheNilObj' : undeclared identifier

src\ooSQLite.cpp(1582) : error C2065: 'TheNilObj' : undeclared identifier

src\ooSQLite.cpp(1586) : error C2065: 'TheNilObj' : undeclared identifier

src\ooSQLite.cpp(1664) : error C2065: 'TheNilObj' : undeclared identifier

src\ooSQLite.cpp(1735) : error C2065: 'TheNilObj' : undeclared identifier

src\ooSQLite.cpp(1796) : error C2065: 'TheNilObj' : undeclared identifier

src\ooSQLite.cpp(1863) : error C2065: 'TheNilObj' : undeclared identifier

src\ooSQLite.cpp(1932) : error C2065: 'TheNilObj' : undeclared identifier

src\ooSQLite.cpp(2007) : error C2065: 'TheNilObj' : undeclared identifier

src\ooSQLite.cpp(2074) : error C2065: 'TheNilObj' : undeclared identifier

src\ooSQLite.cpp(2174) : error C2065: 'TheNilObj' : undeclared identifier

src\ooSQLite.cpp(2195) : error C2065: 'TheNilObj' : undeclared identifier

src\ooSQLite.cpp(2254) : error C2065: 'TheNilObj' : undeclared identifier

src\ooSQLite.cpp(2304) : error C2065: 'TheNilObj' : undeclared identifier

src\ooSQLite.cpp(2602) : error C2065: 'TheNilObj' : undeclared identifier

src\ooSQLite.cpp(2670) : error C2065: 'TheNilObj' : undeclared identifier

src\ooSQLite.cpp(2751) : error C2065: 'TheNilObj' : undeclared identifier

src\ooSQLite.cpp(2773) : error C2065: 'TheNilObj' : undeclared identifier

src\ooSQLite.cpp(2782) : error C2065: 'TheNilObj' : undeclared identifier

src\ooSQLite.cpp(3331) : error C2065: 'TheNilObj' :

[Oorexx-users] (no subject)

2014-09-30 Thread Bertram Moshier

Hello David and all others,

 The rexxc program (supplied with ooRexx) can remove the ability of
 anyone from seeing the original source code. But be sure to save a copy
 of the original source as you can not get it back from the code produced
 by rexxc

Thank you so very much!

Bert.
--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users

Re: [Oorexx-users] Reading file opened by a second program

2014-09-30 Thread Bertram Moshier

Hello Rick

 Generally, it is impossible to answer questions
 like this without seeing exactly what you are
 doing.  I can't speak for others, but I won't even
 attempt to answer the is this a bug type
 questions until I have an open bug report and
 am able to reproduce the problem myself.

You are correct.  I posted an example of the code several digests back.
Here it is again:

This is a snippet of code:

fn = 'Ibhalliwell_2014.09.13.log';
call stream fn,'C','OPEN READ SHARED';
input_lines. = '';
do i = 1 to 9 while lines(fn);
  input_line.i = linein(fn);
  end;
input_lines.0 = i - 1;
do i = 1 to input_lines.0;
  say i '-' length(input_lines.i) '-' input_lines.i;
  end;
say input_lines.0;

What I got was an improvement, but 

1 - 0 -
2 - 0 -
3 - 0 -
.
.
.
1498 - 0 -

In this case the program Windower4.exe (http://www.windower.net) is the
one creating / writing the file Ibhalliwell_2014.09.13.log.

Both of the Microsoft Windows (7 / XP x32  x64) type and copy commands
(cmd.exe) successfully read and process the file
Ibhalliwell_2014.09.13.log.  They provide the actual lines in the file,
while the above Rexx code sees the number of lines in the file, but returns
a null line.

Bert.
--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users

Re: [Oorexx-users] Reading file opened by a second program

2014-09-30 Thread Rick McGuire

And this is still not a bug report

Rick

On Tue, Sep 30, 2014 at 8:11 PM, Bertram Moshier bertrammosh...@gmail.com
wrote:

 Hello Rick

  Generally, it is impossible to answer questions
  like this without seeing exactly what you are
  doing.  I can't speak for others, but I won't even
  attempt to answer the is this a bug type
  questions until I have an open bug report and
  am able to reproduce the problem myself.

 You are correct.  I posted an example of the code several digests back.
 Here it is again:

 This is a snippet of code:

 fn = 'Ibhalliwell_2014.09.13.log';
 call stream fn,'C','OPEN READ SHARED';
 input_lines. = '';
 do i = 1 to 9 while lines(fn);
   input_line.i = linein(fn);
   end;
 input_lines.0 = i - 1;
 do i = 1 to input_lines.0;
   say i '-' length(input_lines.i) '-' input_lines.i;
   end;
 say input_lines.0;

 What I got was an improvement, but 

 1 - 0 -
 2 - 0 -
 3 - 0 -
 .
 .
 .
 1498 - 0 -

 In this case the program Windower4.exe (http://www.windower.net) is the
 one creating / writing the file Ibhalliwell_2014.09.13.log.

 Both of the Microsoft Windows (7 / XP x32  x64) type and copy
 commands (cmd.exe) successfully read and process the file
 Ibhalliwell_2014.09.13.log.  They provide the actual lines in the file,
 while the above Rexx code sees the number of lines in the file, but returns
 a null line.

 Bert.





 --
 Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
 Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
 Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
 Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer

 http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
 ___
 Oorexx-users mailing list
 Oorexx-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/oorexx-users


--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users

[Oorexx-users] Is it possible to prevent end-users from reading a REXX program you're giving to them?

[Oorexx-users] Reading file opened by a second program

Re: [Oorexx-users] Reading file opened by a second program

[Oorexx-users] ooSQLite 10584 compile problem

Re: [Oorexx-users] ooSQLite 10584 compile problem

[Oorexx-users] (no subject)

Re: [Oorexx-users] Reading file opened by a second program

Re: [Oorexx-users] Reading file opened by a second program

8 matches

Site Navigation

Mail list logo

Footer information